A Resume Export Checklist for PDF and DOCX
Check the exact resume file before submitting: employer instructions, text reading order, contact links, page breaks and a saved copy of your application.
Updated
Written by Egem Garip
The short answer
Choose the file type the employer requests, then inspect the exact exported file rather than only the editor preview. Check readable text, contact details, page breaks and the application fields populated after upload. A successful local check is not proof that every employer parser will read it correctly. Save the submitted version with the job posting.
Key takeaways
- Employer upload instructions take priority over general PDF-versus-DOCX advice.
- A visually correct file and a correctly read text layer are different checks.
- Review application fields after upload and preserve the exact submitted version.
The last thing to inspect is the file you will submit, not the editing window you just finished using. Downloading, converting or reopening a document creates another opportunity to notice missing text or an awkward page break.
This checklist is our recommended submission routine. It is not a certification of ATS compatibility, and it does not test every recruiting platform. For a US application, start with the employer’s own upload instructions; this page does not replace federal resume requirements or an academic CV format.
Let the application tell you which format to use
Read the accepted file types and size limit before exporting. If a posting asks for DOCX, do not override it with a general tip that PDF is better. If it accepts both, inspect whichever file you intend to submit. Keep an editable working document separately from the submitted version.
There is a difference between accepting an attachment and extracting information from it. Greenhouse’s documentation describes resumes that are attached to a candidate while automatic field extraction fails. It says the candidate details then need to be entered manually. That is evidence about Greenhouse’s parsing workflow, not proof of automatic rejection and not a rule for every ATS.
For that platform’s specific documentation, see the Greenhouse resume guide. Avoid treating an accepted file extension as a guarantee that every field was read correctly.
Open the exported document
Use the file you just downloaded. Inspect every page, including an unexpected second page. Our review list is:
- Your name, phone number and email are complete and current.
- Employer names, titles and dates match the version you intended to submit.
- A heading is not stranded at the bottom of a page, away from its content.
- Bullets, punctuation and special characters are intact.
- Links point to your actual portfolio or profile, not a template placeholder.
- There are no editing comments, unfinished placeholders or irrelevant notes.
A DOCX opened in another editor may not look exactly like the PDF preview. Check its layout separately. In our builder, the live preview is the PDF; exporting Word does not turn that preview into a verification of the Word file.
Check the text, not just the appearance
For a PDF, try selecting and copying its text into a plain-text editor. Read the result from top to bottom. Do experience dates stay with the right job? Does a skill list interrupt a sentence? Are letters joined as words rather than separated into individual characters?
Greenhouse lists columns, tables, headers or footers and letter spacing among possible parsing difficulties. Those are vendor-specific warnings, not evidence that every such document will fail. A copy-and-paste check also has limits: it tells you what your viewer extracted, not what an employer’s parser will extract.
Our resume builder offers PDF and Word export and a parser view for its PDF. The published file checks and resume score explain what they examine. The score does not validate your employment history or predict a hiring decision.
Invented troubleshooting example: a candidate’s name is visible in a decorative header, but the copied text starts at “Experience.” In that situation, our recommendation is to simplify the header, export again and repeat the text check. Do not assume the missing name is harmless because the document still looks good.
Inspect what the application filled in
After uploading, review any editable fields the application populated. Check each role’s title, employer and dates as well as contact details. Correct inaccurate fields where the form allows it. If you cannot correct a problem, use the employer’s instructions or support channel rather than sending repeated speculative versions.
This step does not reveal whether you passed screening. It only prevents you from knowingly leaving an inaccurate application field uncorrected.
Keep the file you sent
Save the exact file alongside the posting and submission date. A simple private naming pattern is Role-Employer-YYYY-MM-DD.pdf; the example is organizational advice, not an ATS requirement. When an interview arrives, practice against that version. The resume question guide helps connect the written claims with what you will explain aloud.
Questions people also ask
Is PDF always better than DOCX for a resume?
There is no universal recommendation here. Use the format the employer requests or accepts, and check the exported file. A local parser result does not establish how the employer’s system will handle it.
Does a successful text check guarantee ATS compatibility?
No. It shows what that particular reader extracted. Other parsers can behave differently, and correct extraction does not establish job fit or guarantee an interview.
Sources
- Unsuccessful resume parse, Greenhouse Support (2026-10-09)
Written byEgem Garip, Resume writer
Egem Garip specializes in resumes and writes about presenting work experience clearly, tailoring applications and preparing to explain resume claims in interviews.
Build a resume you can explain
Edit your experience, check the published resume rules and export your document. Our score is not an employer's ATS score.
Open the resume builder