One of the most confusing parts of job applications is the file format.
Some portals ask for PDF. Some recruiters ask for DOCX. Some ATS platforms accept both but parse them differently. If you choose the wrong format (or export incorrectly), your resume can look perfect to you—but broken to the recruiter.
This guide explains when to use PDF vs DOCX, what ATS systems typically prefer, and the export mistakes to avoid.
Quick answer
- Use PDF for most applications (consistent formatting, looks identical everywhere).
- Use DOCX when the recruiter explicitly asks for it, or when you’re applying through an ATS known to parse DOCX better.
If you’re unsure, send PDF.
Why PDF is usually the safest
PDF keeps your layout stable:
- Fonts
- Spacing
- Bullet alignment
- Columns
- Page breaks
Recruiters often review resumes on different devices (Windows, Mac, mobile). PDF reduces surprises.
PDF is great for:
- Campus placements
- Email applications
- LinkedIn Easy Apply
- Most company career portals
When DOCX is better
DOCX is editable and can be parsed cleanly by some systems.
DOCX is useful for:
- Recruiters who want to add notes or forward your resume internally
- Agencies that standardize resume formatting
- Portals that sometimes fail to parse PDFs correctly
If the job post says “DOC/DOCX only,” follow it.
How ATS reads PDFs vs DOCX
ATS tools are not all the same, but the pattern is:
- DOCX: often easier to parse because it contains structured text
- PDF: can be easy or hard depending on how it was generated
The big PDF mistake
If your PDF is actually an image (like a scanned PDF), the ATS may not extract text.
That means:
- Your keywords don’t get recognized
- Your sections may be empty in the ATS preview
Quick check
Open your PDF and try:
- Select text with your mouse
- Copy/paste into Notepad
If you can’t select text, your PDF is not ATS-friendly.
Resume export mistakes that cause real rejections
1) Using fancy columns without testing
Two-column resumes can look great, but some ATS systems read them in the wrong order.
If your target role is ATS-heavy (MNCs, portals), prefer single-column ATS templates.
2) Using icons as section headers
Icons look modern, but ATS may ignore them.
Use text headings like:
- Summary
- Skills
- Experience
- Projects
- Education
3) Missing spaces / broken bullets after export
This happens when fonts don’t embed correctly or when a tool “flattens” the layout.
Avoid tiny font sizes and ultra-tight line spacing.
4) Over-editing after export
If you export to DOCX and then edit it in a different tool, spacing and page breaks can shift.
If you edit, re-check the final version.
A practical rule for India job seekers
Use this simple decision tree:
- Recruiter explicitly asked for DOCX? → Send DOCX.
- Company portal supports PDF? → Send PDF.
- Unsure? → Send PDF.
If a portal auto-parses your resume, check the preview.
If the preview is broken, try the other format.
PDF vs DOCX: pros/cons table
| Format | Pros | Cons |
|---|---|---|
| stable layout, professional look, best for email/LinkedIn | some ATS parse poorly if export is wrong | |
| DOCX | editable, often parses well in ATS | layout can shift across devices/tools |
How to export correctly (the checklist)
For PDF export
- Use a clean template
- Ensure text is selectable
- Keep margins consistent
- Avoid text-over-images
- Review on mobile + desktop
For DOCX export
- Keep headings simple
- Avoid heavy tables
- Don’t rely on icon fonts for meaning
- Re-open the DOCX in Word/Google Docs and verify spacing
What recruiters actually care about
Recruiters rarely reject because “you used PDF.” They reject because:
- Hard to read
- Missing keywords
- No proof of skills
- Poor structure
Format is the last 5%. Content is the first 95%.
Recommended workflow
- Build resume in an ATS-friendly template
- Export PDF (default)
- If recruiter asks: export DOCX
- Always test on a second device
Export your resume in seconds
With a template-based builder, exporting becomes consistent.
Helpful links:
- Start builder: /builder/content
- Download: /builder/download
- Templates: /templates