Choose PDF or DOCX for the application you are sending

The most useful first question is whether the employer specifies a format. If the vacancy requests DOCX, sending PDF because a generic article calls it safer ignores the instruction. If several formats are accepted, you have room to compare their practical behavior. Check the file-size limit, whether additional documents need separate uploads, and whether a portfolio belongs in a link field rather than the resume attachment.

Greenhouse’s published upload documentation lists both PDF and DOCX among supported candidate formats. Use those published formats as guidance for that platform and check the instructions of the application you are completing. An employer can also provide instructions that narrow the choices offered by a broader system.

Save those instructions beside the application record. You may prepare several applications in one session, each with different requirements. A dependable workflow checks the specific destination instead of applying a remembered preference to every submission. Format selection is a small decision, but the consequences of choosing the wrong attachment can undo careful content preparation.

A PDF is commonly used to preserve a finished page presentation, while a DOCX remains an editable word-processing document. That distinction can guide your workflow, but it does not eliminate the need to inspect either file. A PDF may contain selectable text or page images. A DOCX may use ordinary paragraphs or complex arrangements that behave differently in another viewer.

Keep the original editable document regardless of the format you submit. It is easier to correct a typo, update a date, or create a new application version from that source than to reconstruct text from an exported page. Treat exports as snapshots of a particular version, with clear filenames and an identifiable target.

Avoid repeatedly converting between formats as an editing method. Each conversion can introduce changes that are difficult to track. Make the substantive edit in the source, export the requested format, and inspect the new artifact. The existence of a familiar extension does not prove that the document remains complete, readable, or free of working notes.

Open the PDF independently of the editor and review every page. Look for missing characters, unexpected blank pages, clipped lines, and headings separated from their content. Check the last line of each section, because export problems can be easy to miss when the opening looks correct. Test visible links rather than assuming that their appearance means they work.

Then select and copy text into a plain editor. Inspect contact details, section order, job titles, and dates. The copied text may lose visual spacing while remaining understandable; that is different from losing the name or combining unrelated columns. A local extraction check cannot reproduce every employer’s system, but it can reveal concrete defects in your file.

A scanned page may look excellent while offering no selectable text. If you have the editable source, export from it instead of photographing or scanning the resume. Do not assume that changing the filename from image to PDF creates an equivalent text document. The content inside the file matters more than the label at the end.

Open the DOCX in the intended application and, where practical, another ordinary viewer. Check whether the layout depends on a font that may not be available elsewhere. Inspect page breaks, tab alignment, tables, and long headings. A document that remains understandable after modest visual changes is more resilient than one whose meaning depends on exact positioning.

Remove tracked revisions, comments, alternative wording, and unfinished placeholders from the submission copy. Verify the visible content after doing so. A comment that helped you remember a factual question should not remain inside the file sent to an employer. Keep the working version separately if you need to preserve the editing history.

Do not send an editable file solely because you assume a reviewer wants to modify it. Follow the requested process. If a recruiter explicitly asks for a particular format, provide a checked version while keeping your own record of what you sent. The file format does not change your responsibility for the accuracy of its claims.

A fictional applicant, Sam, has a two-column source document. The PDF looks balanced, but copied text inserts the skills column between the employer name and the job title. The DOCX opens with a different font and pushes a heading onto a third page. Neither artifact is ready merely because its extension is accepted.

Sam simplifies the contact and experience sections into ordinary text, reduces the layout’s dependence on precise positioning, and exports both versions again. The new PDF preserves the intended page layout and produces a sensible text sequence. The DOCX remains readable in the second viewer. Sam then submits the format requested by the employer rather than declaring one format universally superior.

The important result is observable: specific problems were found and corrected. Describe the changes you verified: restored text, corrected order and intact contact details. The applicant has verified the artifact under the available checks and complied with the destination’s instructions.

Renaming a file changes its label. Exporting or converting creates a different representation. Compressing aims to reduce size. These operations solve different problems. Replacing .docx with .pdf in the filename does not perform a genuine conversion and may leave a file that cannot be opened correctly.

If a file exceeds an upload limit, identify what is making it large. A resume made primarily of text rarely needs oversized images. Remove unnecessary visual assets or export with sensible image settings rather than relying immediately on an unfamiliar online service. Any service receiving the document receives the personal information it contains, so use a workflow you understand and have chosen deliberately.

After a genuine conversion or compression, repeat the relevant checks. Confirm that text remains selectable, links still work, and pages are complete. Do not keep several almost-identical exports in the submission folder without clear labels. The final attachment should be the inspected artifact, not an earlier version that happens to have a similar name.

Where an application portal displays a preview or extracts fields, inspect the result before submitting. A successful upload confirms that a file was accepted at that step; it does not confirm that every date or title was interpreted correctly. Correct populated fields where the form allows and compare the final answers with the resume.

One documented example shows why upload and parsing are separate checks. As reviewed on October 17, 2026, Greenhouse lists DOC, DOCX, PDF, RTF and TXT as supported candidate document formats, with uploads up to 100 MB. Its separate unsuccessful-parsing guidance says resumes larger than 2.5 MB cannot be parsed. A file can therefore meet that product’s upload limit while exceeding its parsing limit. These are Greenhouse’s published limits, not a rule for every employer or application system.

In its recruiter-facing workflow, Greenhouse explains that when parsing fails, the resume can remain attached while candidate details require manual entry. A parsing failure is therefore not, by itself, evidence of an automatic rejection. Check any fields the application presents, follow the employer’s instructions and use the relevant support route if an error prevents completion. The two Greenhouse source documents are linked at the end of this guide.

If the portal does not provide a preview, acknowledge that limitation in your own process. Follow the instructions, use a clear document, and avoid endless speculative edits based on rumors about the software. A reproducible local test is more useful than an unexplained compatibility score that claims to predict an unseen employer’s decision.

When an upload fails, read the actual error. An unsupported extension, excessive size, or interrupted connection calls for a different response from a content problem. Make the smallest relevant correction and retry once the cause is understood. Preserve the original source so troubleshooting does not become a chain of destructive conversions.

Start with one verified source document and export a PDF and a DOCX without changing the content between them. Name the files so you can distinguish the formats while keeping the version identity clear. Write down the employer’s accepted types and any stated size limit. This is a comparison of actual artifacts, not a vote for the extension you have used most often. If only one type is requested, the other can remain a diagnostic comparison rather than an extra attachment.

Open each artifact independently and inspect the same locations: contact block, longest role heading, a bullet containing punctuation and numbers, education status, and the final page. Record specific differences. A changed line wrap may be harmless; a date visually attached to the wrong role is not. A fictional applicant might discover that a custom font causes a DOCX heading to wrap while the PDF preserves it. That observation identifies a local problem without establishing a universal format hierarchy.

Copy representative text from each file into a plain editor where your tools allow it. Compare the recovered characters and sequence with the visible page. Check email addresses, links, and any special symbols used as separators. If the copied text is incomplete, inspect whether the source uses images or floating elements for essential information. Correct the source structure and repeat the export rather than attempting to hide the defect behind a different filename.

Test the links and confirm that the artifact contains no comments, revision marks, or unused placeholders. If you have to compress a file to meet a limit, treat the compressed result as a new artifact requiring inspection. Do not assume that a visually similar preview proves that every page or link survived. Keep the original source and the inspected output separate so a correction can be made cleanly without a chain of conversions.

Select the requested or most suitable accepted format based on the checks, then attach that exact file. Where the portal offers a preview or extracted fields, inspect them as another distinct step. Record which format was sent and preserve the artifact. Your conclusion should be narrow and factual: the file met the stated requirements and passed the checks you performed. Record the format you sent and the checks you completed.

Keep three states distinct: the editable source, the checked export, and the file actually submitted. For a simple application these may live in one folder, but their names should make the relationship clear. Record which artifact went to which opportunity, especially if you produced both PDF and DOCX versions.

Before attaching, confirm the candidate name, role, format, and modification date. Open the file from the location the file picker will use. This catches a common administrative mistake: inspecting one export and attaching another. If you make a last-minute content change, regenerate and recheck the export instead of assuming the previous inspection still applies.

The format decision is complete when the employer’s requirement is satisfied and the artifact passes your visual and text checks. Save the editable source for future tailoring. Keep the verified export and make later edits in the original source document.