Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 — Update released for Drupal core (11.3.7)! drupal 11.2.11 — Update released for Drupal core (11.2.11)! drupal 10.6.7 — Update released for Drupal core (10.6.7)! drupal 10.5.9 — Update released for Drupal core (10.5.9)! cms 2.1.1 — Update released for Drupal core (2.1.1)! drupal 11.3.6 — Update released for Drupal core (11.3.6)! drupal 10.6.6 — Update released for Drupal core (10.6.6)! cms 2.1.0 — Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 — Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 — Minor update available for module menu_link_attributes (8.x-1.7). eca 3.1.1 — Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 — Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 — Minor update available for module ai (1.3.3). ai 1.2.14 — Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 — Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 — Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 — Minor update available for module klaro (3.0.10). klaro 3.0.9 — Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 — Minor update available for module layout_paragraphs (2.1.2). geofield_map 11.1.8 — Minor update available for module geofield_map (11.1.8).
← All modules

doc_to_html

4 sites Security covered
View on drupal.org

Doc to HTML — Usage and Configuration Guide (2.x)

The Doc to HTML module allows editors to upload DOC/DOCX files
directly from a node edit form and automatically convert them into HTML stored in a
text_long or text_with_summary field.

Requirements

The module relies on LibreOffice being available on the server and callable
from the command line. Drupal invokes LibreOffice via a configurable command (for example
soffice or libreoffice) to perform the DOC/DOCX → HTML conversion.

  • Install LibreOffice on the same environment where your Drupal PHP runtime
    is executed (web server or container).
  • Make sure the LibreOffice binary is available in the PATH of the web/PHP user, or
    note its full absolute path (e.g. /usr/bin/libreoffice).
  • From the command line, you should be able to run a simple test such as
    libreoffice --version (or the equivalent binary) without errors.

Example DDEV configuration (config.yaml)

On local environments that use DDEV, you can install LibreOffice inside the
web container by adding an extra package to your config.yaml: 

name: doc-to-html
type: drupal11
docroot: web
php_version: "8.3"
webserver_type: nginx-fpm

webimage_extra_packages:
  - libreoffice

With this configuration, DDEV will install libreoffice inside the web container,
so that the Doc to HTML module can execute the LibreOffice command via CLI.

Global Module Configuration

Before using the widget on content types, you must configure the global settings
used by the Doc to HTML module. These settings are shared by all fields that use
the widget.

Typical global configuration steps:

  1. Define the LibreOffice command
    Specify the command that Drupal should execute to run LibreOffice.
    This can be either:
    • The bare command name (e.g. libreoffice or soffice), if it is in the PATH.
    • The full path to the binary (e.g. /usr/bin/libreoffice).
  2. Define base settings for all fields
    Configure the base (global) options that will be inherited by every field using the
    Doc to HTML widget. These may include:
    • Default output format produced by LibreOffice.
    • Default body extraction regex (to extract the content inside the <body> tag).
    • Optional DOM post-processing rules to clean or transform the generated HTML.
    • Timeouts or command options for the conversion process.

    These global settings act as a “baseline” that individual fields can reuse.

Testing the Conversion with TestWizard

The module provides a TestWizard tool to validate your configuration
and see a live preview of the extraction and conversion process.
This is useful to verify that LibreOffice is correctly reachable and that
the regex settings behave as expected.

Using the TestWizard typically involves:

  1. Navigate to the Doc to HTML test wizard page in the Drupal administration UI.
  2. Upload a sample DOC or DOCX document using the wizard form.
  3. Run the conversion to see:
    • The raw HTML generated by LibreOffice.
    • The extracted <body> segment after applying the body regex.
    • The final HTML after any DOM regex or post-processing pipeline is executed.

The TestWizard uses the global configuration, so any changes you make there will
be reflected in the test results. Once the test behaves as expected, you can move on
to enabling the widget on content fields.

Enabling the Widget on Content Fields

After configuring the global settings and validating them with the TestWizard,
you can enable the Doc to HTML widget on specific fields in your content types.

The widget is designed to work with:

  • text_long fields
  • text_with_summary fields

To enable the widget for a given field:

  1. Go to Structure → Content types and select the content type
    you want to configure.
  2. Open the Manage form display tab.
  3. Locate the text_long or text_with_summary field that should
    receive the converted HTML from DOC/DOCX files.
  4. In the widget selector for that field, choose
    “Doc to HTML” as the widget.
  5. Save the form display settings.

How the Doc to HTML Widget Works

Once the Doc to HTML widget is enabled for a field, the node edit form changes its behavior:

  • The widget adds a virtual upload field used only to upload the
    DOC/DOCX file. This virtual field is part of the widget UI and is not stored
    as a separate field on the node.
  • When an editor uploads a document and saves or updates the node, the module:
    1. Receives the uploaded DOC/DOCX file through the virtual upload element.
    2. Calls LibreOffice (using the globally configured command) to convert the file to HTML.
    3. Extracts the <body> content using the configured body regex.
    4. Optionally applies DOM regex rules or a post-processing pipeline for cleanup and normalization.
    5. Writes the final HTML into the target text_long or text_with_summary field of the node.
  • The uploaded file itself is treated as an intermediate input used only for the conversion.
    The canonical source of content for the node becomes the converted HTML stored in the text field.

Typical Workflow Summary

  1. Install LibreOffice on the server (or container) and ensure it is callable from the command line.
  2. Configure the global Doc to HTML settings:
    • LibreOffice command / binary path.
    • Default body extraction regex.
    • Optional DOM regex / post-processing options.
  3. Use the TestWizard to upload sample documents and validate:
    • That LibreOffice works as expected.
    • That the extraction and cleanup produce the desired HTML.
  4. On each content type that should support DOC/DOCX import:
    • Use a text_long or text_with_summary field.
    • On Manage form display, select the Doc to HTML widget for that field.
  5. Editors can now:
    • Upload DOC/DOCX files via the Doc to HTML widget on the node edit form.
    • Let the module convert and inject the HTML into the text field automatically.
    • Optionally refine the converted HTML directly in the editor (CKEditor) if needed.

With this setup, the Doc to HTML module provides a consistent and configurable workflow
to convert Word documents into clean HTML content inside Drupal, leveraging LibreOffice
and the Drupal Form API.

Activity

Total releases
1
First release
Nov 2025
Latest release
4 months ago
Release cadence
—
Stability
0% stable

Releases

Version Type Release date
2.0.0-rc1 Pre-release Nov 21, 2025