Should You Submit a Word File or PDF for Proofreading?

Was vor dem Versand der Worddatei geprüft werden sollte

Not every DOCX file is automatically well prepared. Use a single, consistent document rather than multiple partial versions wherever possible. Remove old comments that are no longer relevant, and establish a clear file name with a version indicator. If several people are involved, it should be clear which version serves as the working basis.

It is also advisable to activate track changes before sending the document, rather than accepting all previous changes unchecked. This keeps visible how the text developed and which points are still open. For academic texts, the bibliography, footnotes, and tables should be created as genuine elements within the document, not as inserted images.

Another point is frequently underestimated: manual blank lines, spaces used for alignment, or hard line breaks can disrupt the layout at a later stage. They also make revision unnecessarily error-prone. Anyone working with style sheets creates a reliable foundation for editing, typesetting, and export.

When a PDF is the better choice for editing

A PDF is the right file when the focus is no longer on the flow of text but on how content appears on the page. This applies, for example, to the final proof of a book, an already designed magazine, a report with complex tables, or a document containing many graphics. Here it is possible to check whether headings break at unfavourable points, footnotes slip onto the wrong page, or an image is positioned too close to the text.

Typographic details also become apparent in a PDF. Are em dashes, quotation marks, and special characters used correctly? Are hyphenations sensible? Does the typesetting appear balanced on every page? Are there orphaned or widowed lines at the beginning or end of a chapter that disrupt the reading flow? A Word view can only answer these questions to a limited extent, because line breaks may shift depending on the device, font installation, and print settings.

For a final review, the PDF is therefore not merely an export format. It is the definitive view of what readers will ultimately see. For publication-ready projects, it should be reviewed in full once more after all text changes have been made.

The limitations of PDF editing

Comments and annotations in a PDF are well suited for targeted corrections. However, more extensive revisions quickly generate additional effort. Any longer replacement text can alter line breaks, cause text frames to overflow, or require a page to be reset. The actual change must then frequently be replicated in the source file and the document exported again afterwards.

Scanned PDFs are particularly problematic. They often consist solely of image data and contain no reliably editable text. Even with technically generated PDFs, fonts may be embedded or the reading order in multi-column layouts may be complex. For comprehensive editing, such files are rarely the most efficient basis.

The reliable workflow: editable first, then definitive

For most projects, a two-stage workflow proves effective. First, the Word file is revised linguistically and in terms of content. Then all accepted changes are transferred into a clean final version. Only after that comes the export to PDF and the review of layout, page breaks, tables of contents, tables, figures, and print readiness.

For shorter texts, this process can move quickly. For novels, dissertations, or extensive specialist publications, it is worth consciously separating the phases. Otherwise, work is done on a paragraph that behaves visually quite differently after the next page break. A clear version logic prevents accidentally continuing to work with an outdated version.

scribigo supports this process with editing directly in the document: text corrections, style notes, structural work, and content analysis remain where you can review and continue working on them. For the step towards publication, further preparation through to typesetting and the final file can then be usefully added.

Special cases: What applies to academic and designed files

For theses and dissertations, the Word file is almost always the starting point for editorial work. This is especially true when citation style, terminology, and argumentative structure are to be reviewed. Before submission, you should nevertheless check the final PDF, as page numbers in the table of contents, figure captions, and page breaks can change right up until the last moment.

For designed books or catalogues, the situation is different. If the typesetting has already been created in a layout programme, the PDF is often the authoritative review version. Text changes should then not only be made as free annotations, but clearly marked with page, paragraph, and the desired adjustment. Implementation should subsequently be carried out in the source file of the typesetting, so that no conflicting versions arise.

A PDF may also be necessary for forms, contracts, or templates with a protected layout. In that case, the objective should be precisely defined: if the aim is exclusively linguistic corrections, an annotated PDF version is often sufficient. If the text is to be fundamentally revised, an editable source file is a significantly better basis.

The best file is the one that makes decisions visible

The choice between Word and PDF is not a matter of preference. It determines whether editorial work remains traceable and whether the final design is genuinely reviewed. A Word file creates space for improvements to the text. A PDF provides certainty for the final view of the page.

When you hand over your document, therefore always state the desired scope of the review and the current stage of editing. A clear working file for changes and a definitive PDF version for the final check give your text exactly what it needs before publication: an orderly path from revision to the finished page.