What Is an HWP File? A Plain-English Guide

HWP is Hancom’s native word-processing document, most often encountered in Korean workflows

An .hwp file is a document made by Hancom’s Hwp word processor. It can contain the things expected in a full document file: typed text, character formatting, fonts, page type and margins, tables, pictures, equations, charts, forms, and drawing objects. HWP should not be confused with HWPX. HWP is the established binary format; HWPX is Hancom’s newer open XML-based document format. Hancom says it has supported HWPX since 2010 and changed its default format to HWPX in 2021, but large collections of earlier and continuing documents still use the .hwp extension.

The HWP 5.0 specification published by Hancom is unusually useful for understanding why an HWP is not plain text. It says version 5.0 is based on the Windows Compound File structure, stores most character information as Unicode UTF-16LE, and uses zlib compression for the body text and picture-related data. The format also keeps uncompressed basic information. In other words, readable Korean text may be inside the file, but a text editor cannot reliably locate it or understand the surrounding structure. A capable HWP reader must interpret the compound-file streams, compression, document records, and page instructions.

HWP, HWPX, and DOCX can carry similar pages while using different document models

HWP 5.0 is a compound binary document, whereas DOCX and HWPX are XML-based package formats. They can all represent paragraphs, tables, pictures, and page formatting, but the internal names, layout rules, and object models are not identical. A conversion therefore reconstructs the destination’s idea of a document; it does not simply rename a file. A font choice, line-breaking rule, object anchor, table size, or equation can be represented differently even when the words are transferred correctly. The closer the source stays to basic paragraphs, ordinary tables, and common pictures, the more predictable the result tends to be.

Hancom’s own compatibility guide makes this limit concrete. When Hwp saves to DOCX, it lists possible differences with equations, proofing symbols, form controls, table sizes, font shadows, partial underlines and strikethroughs, outline and border/background effects, spread alignment, line spacing, and paragraph borders. In the other direction, it lists issues with table merges, charts, drawings, WordArt, organization charts, SmartArt, and OLE objects. These are not vague warnings about “formatting.” They identify the objects worth inspecting on the rendered pages after conversion.

Changing an extension from .hwp to .docx or .hwpx does not perform this translation. It leaves the original compound-file streams in place and can make the destination application reject or misidentify the file. Use an application or converter that truly reads HWP and writes the target format, retain the original HWP, and compare the result rather than assuming that a familiar extension changes the underlying format.

The decision to retain, convert, or publish an HWP has concrete consequences

• Keep HWP for native editing: Hancom-specific objects and layout settings have the best chance of remaining faithful in the application that produced them.
• Choose HWPX for a newer Hancom format: it is the XML-based successor and has been Hancom’s default since 2021, but it is still not the same package format as DOCX.
• Choose DOCX for Word editing: text and common layout can transfer, while equations, forms, complex tables, drawing effects, and OLE content need review.
• Choose PDF for fixed reading or printing: it avoids requiring the reader to support HWP editing, but it is not a replacement for the editable source.
• Choose TXT only for wording: it removes page layout, tables as tables, pictures, and document objects, so it is unsuitable for a visual form or report.
• Preserve the original: converting back from an edited DOCX or PDF cannot reliably reconstruct every HWP-specific object or layout decision.

The right target depends on the recipient’s action. A recipient who must make a new native Hwp document needs HWP or HWPX; someone who must revise ordinary prose in Microsoft Word may need DOCX; someone who only needs a dependable page view needs PDF. This is a compatibility choice, not a claim that one format is universally better. Send the least complicated format that still preserves the action the recipient must take.

Hancom applications are the reference environment; other readers need format-specific testing

Hancom’s own products are the reference environment for HWP. Its WebHwp developer documentation lists support for HWP, HWPX, HWPML/HML, ODT, PDF, and XML; Hancom Office for Android says it can open and edit .hwp and .hwpx along with DOCX, XLSX, PPTX, PDF, CSV, and TXT. That support is meaningful when a document contains Korean typography, Hancom tables, forms, or page layout that must be edited, not merely viewed. A viewer that extracts the text is not automatically an editor that preserves the full document.

Microsoft Word does not use HWP as its native document model. When an HWP is supplied to a Word-only environment, use an approved HWP-capable conversion path and inspect the result in Word. Hancom also offers a Microsoft Word Compatible Document mode, where layout options such as line spacing and spacing width change toward Word’s layout rules. That setting can help plan a future DOCX exchange, but it cannot make all object models identical. For a document with strict visual requirements, PDF is a useful companion delivery file after the editable conversion has been checked.

Specific HWP conversion failures reveal what needs to be fixed before sending

Korean characters show as boxes, blanks, or unrelated symbols. The HWP 5.0 specification uses Unicode UTF-16LE for most character information, so the stored text is not limited to a legacy Korean code page. The visible failure is often the reader’s font or text-rendering environment, not proof that the text vanished. Open the source in Hancom first, verify the characters, then test the converted document on the same type of application the recipient will use. If a required Korean font cannot travel, choose an available substitute and recheck line wrapping and page count.

Tables, equations, or drawings shift in DOCX. Hancom documents these precise compatibility limits: table size, form controls, equations, paragraph spacing, borders, and text effects can differ when saving to DOCX. Simplify the source where possible, avoid relying on partial formatting effects for essential meaning, and inspect each affected page. If the visual layout is legally or operationally important, provide a PDF reference copy alongside the editable DOCX instead of trying to correct a converted Word file by guessing.

An HWP opens as a damaged file or produces unreadable raw text. Do not open it in a plain text editor as a normal troubleshooting step. The file is a compressed compound document, not a character stream. Confirm the original extension, make a copy, and try a current Hancom reader or a conversion tool with HWP support. If it fails there too, treat it as possible file damage and ask for a fresh copy or a PDF/HWPX export from the sender. A file that merely has the wrong extension must be corrected at the source, not renamed blindly.

HWP format choices are easier to compare by the action they preserve

Questions that help decide what to do with an unfamiliar HWP attachment

Is HWP the same as HWPX?
No. HWP is Hancom’s established binary format; HWPX is its newer XML-based format. Hancom made HWPX its default in 2021, but both extensions remain important in real collections.

Can I open HWP by changing its extension to DOCX?
No. HWP 5.x uses a compressed compound-file structure, not the DOCX XML package. Rename does not translate its streams or document records.

Why did only the table layout change in the Word copy?
Hancom specifically warns that table sizing, merges, spacing, and other objects can differ between Hwp and Word. Compare the conversion visually and repair the source or destination deliberately.

Can I extract just Korean text for translation?
Yes, TXT can be appropriate when only wording is required. Verify character encoding and retain the original because pictures, layout, and table structure do not survive as plain text.

What should accompany an editable converted file?
Keep the original HWP and, when visual fidelity matters, add a PDF reference. This makes a layout difference visible without pretending conversion is lossless.