HWPXDOCX

Convert HWPX to DOCX in your browser

Convert HWPX directly to editable DOCX without an intermediate HWP save. HanOpen reads the OWPML package, follows its document sections and writes Word parts locally in your browser, without uploading your document.

Your file never leaves this device.

Drop files here

Accepted: .hwpx. Several files at once are fine.

Up to 200 MB per file on this device.

Files (0)

Output:DOCX

No files yet. Drop one above or choose from your device.

Options

Font name to write into the DOCX

Word looks up a font by name for every run of text. Hangul characters survive either choice; this only decides which name Word is told to use.

Waiting for a file.

The download button appears here once a conversion finishes.

Conversion summary

After a conversion this card lists what was detected and what was written to the output.

Layout, line breaks and font positions are not preserved.

How to use it

Add the original .hwpx attachment, keeping its package intact, and select the font mapping for your DOCX copy.
Run the converter to read the package manifest, styles, section content and embedded image references in document order.
Save the DOCX output and compare section boundaries, merged tables and notes with the source using the per-file conversion summary.

What is preserved

HWPX provides table cell addresses and spans in XML and links pictures through binary item references. The converter translates those structures to DOCX, reports unsupported parts and stops if the section body is encrypted. The summary’s counts identify represented elements; they are not a guarantee of unchanged pagination.

HWP element	In this output
Paragraphs and text	Kept as structure and formatting
Character formatting	Kept as structure and formatting
Tables	Kept as structure and formatting
Merged cells	Kept as structure and formatting
Text boxes and shapes	Kept with simplified formatting
Images	Kept with simplified formatting
Footnotes	Kept as structure and formatting
Endnotes	Kept as structure and formatting
Headers	Kept with simplified formatting
Footers	Kept with simplified formatting
Numbering and bullets	Kept with simplified formatting
Equations	Kept as plain text
OLE objects	Replaced with a placeholder
Charts	Replaced with a placeholder
Distribution-only documents	Not included; a notice is shown
Password-protected documents	Not included; a notice is shown

This guide describes what the tool handles. Review the result and any warnings before using your output.

About the formats

HWPX is an XML-based document package using OWPML. Its ZIP container can hold a package manifest, document-wide definitions, section XML and binary assets. DOCX is also a ZIP of XML parts, but the two formats use different structures and relationships. HanOpen follows the HWPX package ordering and resolves references before building a DOCX document; changing the extension or simply moving XML files would not perform that mapping. Our collected real-document corpus contains fifteen documents, eleven HWP 5.0 and four HWPX, so the presence of one format does not establish that every attachment from the same source uses it.

Frequently asked questions

Is an HWPX file just a newer HWP filename?: The container and content structures differ: HWP 5.0 is binary, while HWPX contains OWPML XML in a ZIP package. Use the original extension to select the appropriate tool. The converter also checks the file’s actual contents, because an extension alone cannot prove its format.
Should I convert HWPX to HWP first?: That intermediate step is unnecessary for this tool. It reads the HWPX package directly, including its manifest, definitions and body sections. Keeping the source package avoids introducing another save operation whose changes you would also need to review.
Which HWPX results have been measured?: The September 7, 2026 corpus run converted ten readable HWPX samples to DOCX and opened all ten in Word 16 without repair. Their table counts matched and measured text coverage reached at least 99% for each file. One additional HWPX sample had an encrypted body and was rejected. These are corpus observations, not a promise for every HWPX export.
Why can the package open as ZIP but conversion still fail?: Being able to list a ZIP does not mean its section XML is readable or its document references are valid. An encrypted body can sit inside an otherwise accessible package. Missing sections, malformed XML or unresolved required package parts can also prevent document conversion.
How are embedded pictures handled?: The section references identify the corresponding packaged image data. Supported PNG, JPEG, GIF and BMP images are included in DOCX; externally linked images are reported and not fetched. WMF and EMF are replaced with placeholders. The preview picture stored in a package is not treated as a substitute for the complete document.
Do sections and notes remain available for editing?: Represented section settings, table cells, footnotes and endnotes are written into DOCX structures. Some header, footer and numbering behavior is simplified, and text boxes and floating pictures can move. Review section transitions and note references in the destination editor before relying on the document’s layout.

Keep the document package together

Select the downloaded .hwpx file itself, not a section XML extracted from it. Paragraph text may depend on document-wide character definitions, table styles and image relationships elsewhere in the package. Extracting a single XML file discards those connections. If the downloaded attachment is incomplete, obtain a fresh copy rather than attempting to repair its structure by renaming files inside the ZIP.

Inspect tables with spans and nesting

HWPX cell addresses describe where a cell starts, while its spans describe how many rows or columns it covers. DOCX has its own grid representation, so the converter maps the logical structure instead of copying the source XML verbatim. After opening the result, check an ordinary table and a complex table separately. Pay particular attention to nested content, long merged headings and cells which appear blank because another cell spans across them.

What the font choice controls

The selected preset supplies font names for the generated DOCX. Retaining original names keeps those references but does not deliver the fonts to another computer. The recipient’s available fonts and editor determine the final line breaks. If a heading wraps differently, compare its font first before changing every paragraph’s size or manually inserting line breaks throughout the file.

Separate structure from visual fidelity

A readable XML source is useful for identifying document structure, but it does not remove layout differences between formats. Keep the original beside the result when checking approval forms, page-oriented reports or embedded figures. The conversion summary helps locate partial support; a successful result means a DOCX was generated from the readable source, not that every rendered page was independently approved.

Other options

If the sender can provide the underlying editable DOCX, compare that copy with the HWPX attachment before choosing your editing source. For reading alone, open the HWPX in HanOpen’s viewer. If the destination needs plain text or a documentation format, choose HTML, TXT or Markdown directly from the original package instead of repeatedly converting the same intermediate DOCX.