WORKFLOW GUIDE

Choose the right document workflow before you upload anything

“Convert this file” is not one task. Viewing, extracting text, saving a PDF, checking writing signals, counting characters, shrinking an image, and bundling files have different risks and different best tools. Start with the outcome you need, then choose the smallest workflow that can produce and verify it.

Start with the result, not the file extension

A file extension tells you what a file is called; it does not tell you what you need to do with it. If you only need to read a PDF, opening it locally is safer and faster than converting it again. If you need a submission-ready PDF from a text-based file, a print workflow is appropriate. For a legacy HWP document, start with an HWP-aware local preview, then compare the saved PDF with Hancom Office when the original layout must match exactly.

The same distinction applies to writing checks. A reference score can point to patterns worth revising, but it cannot prove who wrote a paragraph. The useful workflow includes a human reading pass and, for important work, the draft history and source notes.

A decision map for common document tasks

Your goalStart withVerify before you finish
Read an existing PDFBrowser PDF viewerPage breaks, fonts, links, and the final page count
Save HWPX, HTML, Markdown, or text as PDFLocal preview and print to PDFPaper size, margins, headers, tables, and the saved PDF
Convert a legacy binary HWPDocument Forge's local HWP previewRendered pages, fonts, tables, and the saved PDF; compare with Hancom Office when layout is critical
Review whether prose has repetitive patternsWriting-signal referenceSample length, language, draft history, and a human review
Meet an application character limitCharacter counterThe destination form's own rule for spaces, line breaks, and emoji
Send a smaller image or a group of filesImage compression or ZIP bundlingThe measured output size and whether the recipient can open it

Three worked choices

1. A Korean application form asks for a PDF

First identify whether the source is HWP, HWPX, DOCX, or already a PDF. For HWPX, preview the extracted text and use the browser print dialog to create a PDF. Set the paper size expected by the form, keep the scale at the intended value, and open the saved file again. Count the final text separately if the form has a character limit. Keep the original document beside the PDF until the upload is accepted.

2. A manager asks whether a draft “looks like AI”

Do not turn a detector number into a personnel decision. Use a writing-signal check only as an editing prompt: look for unusually uniform sentence lengths, repeated connectors, generic transitions, and paragraphs that all end in the same rhythm. Compare the current draft with the author's notes and earlier versions. If the question affects employment, grading, or discipline, use a qualified human review and the normal evidence process.

3. An email rejects a file because it is too large

Check the actual largest file first. JPEG, PNG, MP4, PDF, DOCX, XLSX, and HWPX are already compressed in common cases, so putting them in a ZIP may only bundle them. A phone photo usually benefits from resizing or a measured WebP/JPEG export. A set of plain text, CSV, logs, BMP, or SVG files may benefit from ZIP compression. Compare the output bytes; never rely on a percentage that was not measured from your files.

When a browser-first path is the safer choice

Browser processing is a good default when the task is previewing HWP or HWPX, reading text, counting characters, checking a PDF, compressing an image, or creating a ZIP. The file can stay in the current session, which removes an upload and a retention policy from the decision. It does not make the device automatically safe: shared computers, browser extensions, downloaded copies, and the destination you eventually send the file to still matter.

Use a server-assisted converter only when the file format or fidelity requirement genuinely needs it. Before selecting one, look for an identifiable operator, a clear privacy notice, a retention period, a supported-format list, an error path, and a way to delete or avoid stored uploads. A service that claims to convert every format perfectly without describing its boundary is not giving you enough information to verify the result.

Finish with a verification pass

  1. Open the output from the beginning, not only the first page.
  2. Check non-Latin text, punctuation, links, tables, and page breaks.
  3. Compare the output size with the original and confirm the filename and extension.
  4. For writing analysis, read the explanation and record the sample length; do not save only the score.
  5. Keep the original and remove temporary copies from shared devices when the task is complete.

Document Forge follows this boundary in the interface: local browser tools show what they actually extracted or measured, supported binary HWP files are rendered locally and shown before PDF saving, and the writing result is labelled as a reference signal rather than a verdict. See the about page for the implementation boundaries and the privacy notice for the data paths.