HWP versus HWPX: what changes the PDF workflow?
HWP is the older binary document format used by Hancom Office. HWPX is the newer, XML-based format. An HWPX file is a ZIP archive containing structured document parts, so a browser can extract text and build a print view without installing an office application. An HWP file is a proprietary binary format, so it needs a format-aware renderer. Document Forge loads that renderer in the browser, creates a local page preview, and opens the browser's own print dialog when you choose to save a PDF.
The extension is a useful first clue, not proof of the file's contents. Renaming report.hwp to report.hwpx does not change the internal format. If a file was renamed by email software or an export process, keep a copy and inspect it with the application that created it before choosing a converter.
Choose the path that matches the document
- Existing PDF. Open it in a browser viewer and check the pages. There is no reason to convert a PDF just to read it.
- HWPX, HTML, Markdown, or plain text. Preview the readable content in the browser, then use the print dialog to create a PDF.
- Legacy binary HWP. Use a renderer that explicitly supports HWP, states whether the file stays local, and explains its fidelity limits. A real renderer can give you a local page preview, but it still needs a visual check before you rely on the PDF.
A practical HWP or HWPX-to-PDF workflow
- Keep the original. Work from a copy and do not overwrite the source with the first PDF export.
- Preview the rendered pages. Confirm that headings, paragraphs, list items, images, and important non-Latin characters are present. If the file contains complex layout, embedded fonts, charts, or tracked changes, compare the preview with the original application.
- Set the print context. Choose the required paper size, scale, margins, headers, footers, and background setting. A browser print dialog is part of the conversion; it is not an invisible default.
- Reopen the saved file. Scroll through every page and check the first and last page, tables, signatures, links, and page numbers before sharing it.
What can change during conversion?
A text-focused conversion can preserve words while changing visual details. Page breaks, tables, footnotes, headers, embedded objects, fonts, line spacing, and text boxes are the common trouble spots. A heading may move to the next page, a table may split, or an unavailable font may change the wrapping. For a contract, official submission, or document with complex tables, keep the original file and verify the PDF visually before sending it.
Example: an application form
For a one- or two-page application, check the form's paper size before printing and make sure the exported PDF still has the expected page count. If the form also specifies a character limit, use the character counter on the final text, then paste it into the destination form once more. The counter and the form may treat spaces, line breaks, or emoji differently.
Example: a table-heavy report
For a report with tables or footnotes, treat a clean text preview as only a first check. Open the source application or a trusted format-aware converter, compare several pages side by side, and inspect the PDF at 100% zoom. If a table is split across pages or a footnote disappears, the PDF is not ready just because it opens successfully.
How Document Forge handles the boundary
Document Forge previews HWP, HWPX, TXT, Markdown, HTML, and existing PDFs in the browser. For HWP, it self-hosts a local renderer, sanitises the generated SVG page image, and uses the browser's print dialog to make the final PDF. The source file is not uploaded by this workflow. This is not a promise that every installed font, table, tracked change, or embedded object will match Hancom Office exactly, so compare the output with the original for a submission where layout matters. Read the privacy checklist before giving any document to a different service.
PDF verification checklist
- Does the page count match what you expected?
- Do Korean, Japanese, Chinese, accented characters, symbols, and equations render correctly?
- Are headings, tables, images, signatures, footnotes, and page numbers in the right places?
- Do important links open the intended destination?
- Does the file name identify the final version, while the original remains available?