PDF vs Word: Which Format Should Your CV Be? (And When)

PDF versus Word is one of the most-Googled CV questions and one of the most consistently misunderstood. The short answer for 2026: PDF is the right default for the vast majority of CV submissions. Word (.docx) is occasionally necessary, almost never preferable to PDF when both are accepted, and the residual fear that ATS cannot read PDFs is a decade-old myth that costs candidates real interviews when they submit broken Word files instead of clean PDFs. Knowing exactly when the exceptions apply, how to generate a PDF that ATS systems parse cleanly, how to name the file so the recruiter can actually find it again, and what to do when the job posting is silent on the question is the difference between a CV that arrives looking the way you designed it and one that arrives looking like a corrupted draft.

Why PDF wins by default in 2026

PDF should be your default format for CV submission in essentially every situation where the employer has not explicitly asked for something else. The reasons are practical, not aesthetic:

Format preservation: a PDF looks identical on every device, in every operating system, with every PDF reader. What you designed is what the recruiter sees. Word documents shift fonts, layouts, margins, and spacing depending on the version of Word, the operating system, the installed fonts, and the printer driver — your carefully designed CV can arrive looking broken without you ever knowing
Mobile readability: roughly 30-40 % of recruiters first scan applications on phones, especially for in-bound applications outside the recruiter's normal working hours. PDFs render cleanly on phones; Word files often do not, especially if the recipient does not have Word installed and the phone defaults to a basic viewer
Edit resistance: PDFs are harder to accidentally modify than Word files. The recruiter cannot inadvertently delete a bullet point while scrolling. This matters more than it seems — accidentally edited Word CVs do circulate
Version control: when you submit a PDF, the version is frozen at submission. Word files can be edited by anyone the recruiter forwards them to, with no audit trail
Universal compatibility: every device, every operating system, every reader. Word requires Microsoft Office, a compatible viewer or an online tool — most professionals have Word, but not all hiring stakeholders do, especially designers, engineers and non-Microsoft-ecosystem teams
Professional convention: in 2026, PDF is the professional default for any business document where format matters. Sending Word when PDF is the convention quietly signals out-of-date file-handling habits

The default rule for 2026: unless the job posting, recruiter or application portal specifically asks for Word, send PDF. The 5 % of cases where this is suboptimal cost you very little (most ATS systems accept both formats with no penalty); the 95 % of cases where PDF is right protect your design and signal current practice.

The ATS parsing myth — when it was true, why it is not now

The single most persistent objection to PDF — that Applicant Tracking Systems cannot parse PDFs — was true around 2010-2014, has been mostly false since 2017, and is essentially false in 2026. The history and the reality:

Early ATS systems (Taleo classic, BrassRing, Kenexa first-gen) had limited PDF text-extraction capabilities. PDFs frequently arrived garbled or unparsed, which is where the myth originated. This was a real problem in its era
By 2018, all major ATS vendors had upgraded their PDF parsing libraries. Workday, Greenhouse, Lever, SmartRecruiters, iCIMS, Taleo Cloud, BambooHR, Recruitee, JazzHR — every modern ATS now parses text-source PDFs at the same fidelity as Word documents
The catch: the PDF must be generated from a text source, not a scan or image. A PDF that is a photo or scan of a printed CV cannot be parsed by any ATS — the text is locked inside an image. Always generate from Word, Google Docs, Pages, LibreOffice, or a CV builder
If you build your CV in Adobe InDesign, Figma, or Canva, double-check that the export is text-PDF not image-PDF. Some design tools default to image export for visual fidelity, which destroys ATS parsing
If you are using a CV-builder app, the output is almost always text-source PDF. Builders are designed for this case
The minority of remaining ATS-parsing issues with PDFs come from unusual layouts — multi-column designs, text in tables, text in text boxes, header/footer text. These can confuse parsers regardless of format. Stick to single-column or simple two-column layouts and the parser will handle the PDF fine

Repeat: 'ATS cannot read PDFs' is wrong in 2026. The candidate who sends a broken Word document because they were afraid the PDF would not parse is solving a problem from 2014 with the wrong tool. If you want to be doubly safe, you can submit both formats when the portal allows multiple uploads — but for most situations, a clean text-source PDF is what wins.

The layout rules that matter more than PDF-vs-Word

The format pipeline — how to generate a PDF that ATS systems love

Not all PDFs are equal. The same content, exported through different tools, can produce a PDF that parses perfectly or one that parses garbage. The reliable pipeline:

Start with Microsoft Word, Google Docs, Apple Pages, or LibreOffice. These all produce text-source PDFs via their built-in 'Save as PDF' or 'Export to PDF' option. This is the most reliable path
If you use a CV builder, the export is almost always already correctly formed. Builders test their PDFs against major ATS systems as part of their product
Avoid: printing your CV and scanning it back. Avoid: taking a screenshot of your CV. Avoid: 'Save as image' or any export that creates a PNG/JPG embedded in a PDF wrapper. All of these create unparseable files
When exporting from Word, use the built-in 'Save As → PDF' option, not 'Print → Save as PDF.' The Save-As path generates a true text-PDF; the Print path on some systems generates a print-rasterised version that is harder to parse
On Mac, both Pages 'Export to PDF' and Word for Mac 'Save As' work correctly. The print-to-PDF path also works on Mac because the OS-level handler is text-aware, but the direct export is still preferable
Test the PDF after export: open it, try to select and copy a sentence. If you can highlight and copy text, the PDF is text-source and ATS-readable. If your highlight selects the whole page as one block, the PDF is image-based and will not parse

The text-selection test takes 5 seconds and is the single best diagnostic for whether your PDF will parse. Do it before every submission, especially the first time you send a CV exported from a new tool. The candidate who skips this test and submits an image-PDF disappears silently into the ATS void with no notification that anything went wrong.

When Word is required — and why to follow the instruction exactly

Despite PDF being the default, there are real cases where Word is required. These are narrow but they do exist. The categories:

The job posting explicitly asks for it. 'Please submit your CV as a Word document' or 'attach a .docx file' is the instruction. Follow it exactly. The cost of compliance is zero; the cost of substituting PDF when Word was requested is rejection at the system level (some portals literally reject non-matching file types) or rejection at the recruiter level (instruction-following is itself a screen criterion)
Government agency applications, particularly in the EU and UK public sectors. Many government HR systems were built on legacy infrastructure and still prefer or require Word for parsing into their case-management systems
Large enterprise HR systems running custom Taleo or PeopleSoft configurations. These are most common in banks, insurance companies, telecoms, energy, pharma, and other regulated sectors with conservative IT environments. The configurations vary, but Word compatibility is more reliably tested than PDF in these stacks
Some legal-sector applications (especially traditional law firms) still prefer Word for editability during the multi-stage approval workflow
Defence and government-contractor applications sometimes require Word with specific metadata stripping for security review
Healthcare HR systems, particularly hospital networks running Lawson or Kronos, often default to Word
Any time you upload to a portal that has separate file-type fields ('Upload CV (.doc, .docx)' explicitly), submit the format requested

The pattern: when an employer or system specifies Word, they have a reason — either parsing infrastructure, editability for review workflows, or compliance requirements. Substituting PDF in these cases either fails outright or signals that you do not follow instructions, both of which are bad outcomes. The cost of obedience is zero; the cost of substitution can be the application.

Recruitment agencies — the one place Word still wins

Recruitment agencies are the most common situation in 2026 where you should send Word rather than PDF. The reason is practical:

Agencies regularly edit your CV before submitting it to their client. The editing is normally light — reformatting into their standard template, removing identifying information for blind submission, adding the recruiter's contact details as the cover header, or adjusting layout for the client's preferred format
All of this requires an editable file. PDFs can be edited but the workflow is clunky, the formatting frequently breaks, and the recruiter ends up retyping sections — which introduces errors. Word is dramatically faster for them
Most agencies will explicitly ask you for Word. If they do not, ask the recruiter their preference at the start of the engagement. 'Should I send my CV as Word or PDF?' is a one-line email; the answer saves friction every time you submit through them
Some agencies have a specific template and will ask you to retype your CV into their template. Send them Word so they can copy-paste cleanly. The template itself is rarely worth resisting — it is how their client expects to receive CVs from them and arguing about it is futile
If you are working with multiple agencies and applying to direct employers in parallel, maintain both formats: a master Word document and the PDF export from it. Update Word, regenerate the PDF whenever you change the master. Never let the two versions drift
If an agency edits your CV in a way you do not like — reformats badly, removes content you wanted, changes phrasing — push back. The CV is still yours; the agency is allowed to format-edit but not to fundamentally rewrite without your sign-off

The two-format maintenance is the small price of working with agencies. The Word file lives at home; the PDF goes to direct employers; both get updated together. The candidate who only has a PDF often discovers when an agency asks for Word that the original Word source has drifted significantly from the current PDF — and now they have to choose between rebuilding the Word file or losing the agency engagement.

How to tailor your CV per application (easier in Word)

The font embedding question — what survives the trip

One of the silent failure modes of CV-sharing is fonts. The font you used to design your CV may not exist on the recruiter's computer, in which case their system substitutes a different font and the layout breaks. Format choice partially solves this:

PDFs embed fonts by default in most modern PDF generators. The font travels with the file. The recruiter sees what you designed even if they do not have your font installed. This is one of PDF's biggest practical advantages
Word files do not embed fonts unless you explicitly enable font embedding in Word's save options (File → Options → Save → Embed fonts in the file). Most people leave this off. The Word file arrives with font names but not the font data; the recipient's system substitutes
If you are going to send Word, either use only universally-installed fonts (Calibri, Arial, Times New Roman, Cambria, Georgia, Verdana, Helvetica) or enable font embedding in the save options
If you are sending PDF, you can safely use a wider range of fonts because they will be embedded. Common professional choices in 2026: Inter, Lato, Open Sans, Source Sans, Garamond, Charter, IBM Plex Sans, Roboto
Avoid: licensed display fonts that cannot be embedded due to license restrictions. The PDF generation will substitute and you will not be told. Stick to fonts with permissive licenses (Google Fonts, system fonts)
Avoid: novelty or decorative fonts even if they render correctly. The font itself is signal — a CV in Comic Sans or a script font reads as unserious regardless of content
Test by opening the PDF on a different device than the one you generated it on. If the layout looks the same, fonts are embedded correctly. If it looks different, something in the font pipeline broke

The font issue is one of the most invisible problems in CV submission — your CV may have looked perfect on your screen and arrive looking different on the recruiter's, and you will never find out. PDF mostly solves this by default; Word requires you to explicitly handle it. This is one more reason PDF wins as the default.

Which fonts read as professional, which silently break

File naming — as important as the format itself

Choosing the right file format is half the battle. The other half is naming the file so the recruiter can actually find it again. This is one of the most underweighted parts of the submission process:

Universal standard: 'FirstName-LastName-CV.pdf'. This is the most useful name in 95 % of cases. The recruiter downloads your file into a folder containing 50 other CVs; yours is the one with your name on it
When tailoring per application, add the company or role: 'FirstName-LastName-CV-CompanyName.pdf' or 'FirstName-LastName-CV-RoleTitle.pdf'. Both make it easier for you to track which version you sent where, and for the recruiter to see this is a tailored application not a mass send
Never use generic names: 'CV.pdf', 'resume.pdf', 'mycv.pdf', 'document.pdf', 'untitled.pdf'. These names disappear into the recruiter's downloads folder among 50 other identically-named files. The recruiter who cannot find your CV when they want to review it 3 days later does not review it 3 days later
Avoid date or version stamps in the filename when submitting: 'JohnSmith-CV-v17.pdf' or 'JohnSmith-CV-2026-03-22-final.pdf' signal disorganisation and amateur file management. The version that goes to the recruiter is 'JohnSmith-CV.pdf' regardless of how many drafts you went through internally
Use hyphens or underscores, not spaces. 'John Smith CV.pdf' often gets URL-encoded as 'John%20Smith%20CV.pdf' when emailed or uploaded, which looks ugly in the recruiter's inbox and is harder to search for later
Match the cover letter file naming if you are submitting both: 'JohnSmith-CV.pdf' and 'JohnSmith-CoverLetter.pdf' as a pair
Avoid special characters in filenames — apostrophes, ampersands, slashes, accented characters. These sometimes break upload portals and can cause email attachment failures in older mail systems. ASCII alphanumeric plus hyphen or underscore is universally safe
Avoid extremely long filenames — 'John-Alexander-Smith-CV-for-Senior-Software-Engineer-Position-at-Acme-Corporation-March-2026.pdf' is worse than 'JohnSmith-CV-AcmeCorp.pdf' even though it contains more information

The naming question feels trivial and gets treated trivially by most candidates, which is exactly why it is a quiet differentiator. The recruiter looking for a candidate they liked two weeks ago, scanning their downloads folder, finds the candidate whose file is named clearly and loses the candidate whose file is 'cv-final.pdf'. The cost of fixing this is 5 seconds; the cost of not is being forgettable.

Where file naming fits in the job-application email

File size — how heavy is too heavy

File size matters more than most candidates realise. The constraints come from email systems, upload portals and recruiter download speeds:

Aim for 0.5-1.5 MB for a clean text-based PDF. This is normal for a 2-page CV with light formatting and an embedded font set. Below 0.3 MB is suspicious (could be image-based or stripped of formatting); above 2 MB is bloated and may have problems
If your CV is over 3 MB, something is wrong. Usually: an oversized embedded photo (compress to 500 KB max), embedded video or audio (remove entirely), embedded design assets at print resolution (export at screen resolution), or unflattened transparency layers from a design tool
Many corporate email systems reject attachments over 10 MB, and some over 5 MB. Recruitment agency systems sometimes reject anything over 2 MB. Portal upload limits vary widely
If your file is large because of a high-resolution photo, downsample the photo to 96-150 DPI. Print resolution (300 DPI) is wasteful on screen and triples the photo's contribution to file size
PDFs can be compressed without quality loss using tools like Adobe Acrobat's 'Reduce File Size' or free online compressors. Compress to a target of 1 MB; check the output to confirm text is still selectable (PDF compression sometimes converts text to images)
Word files are usually smaller than equivalent PDFs because they do not embed fonts and compress text more aggressively. Word's wins on file size, but loses on every other dimension covered earlier

The right target: 0.5-1.5 MB PDF, with embedded fonts, text-selectable, designed for screen rather than print. This file size goes through every email system and uploads to every portal without trouble, and renders fast for recruiters who scan in batches. The candidate whose CV exceeds 5 MB because they embedded a portfolio of work samples should be sending a separate portfolio link, not a giant PDF.

Mobile reading — the 30-40 % who first read on phones

Roughly 30-40 % of recruiters first scan applications on phones, especially for inbound applications received outside working hours. This has implications for format choice:

PDFs render reliably on phones across iOS Files, Android viewers, Gmail's inline viewer, Outlook mobile, and dedicated PDF apps. The layout is preserved exactly as designed
Word files on phones are unreliable. Without Microsoft Office or Google Docs installed and configured, the phone falls back to a basic viewer that often breaks formatting. The recruiter may not bother installing software just to view your CV; they may skip you and come back later, or not
Designs that work on desktop sometimes do not work on phones: dense two-column layouts get squished, small fonts become unreadable, infographics lose detail. Test your CV by opening the PDF on your phone and zooming through it as a recruiter would
Single-column layouts read significantly better on phones than two-column. If you are designing a CV that may be scanned on mobile, the single-column choice is strategic, not just safe
Font sizes that look fine on desktop (10 pt body, 14 pt headings) can be hard to read on phones. Either use slightly larger sizes (11 pt body, 16 pt headings) or accept that mobile readers will be pinch-zooming
Avoid color-on-color designs that have poor contrast at small sizes. A subtle gray-on-white that looks elegant on a 27-inch monitor is unreadable on a 6-inch phone in sunlight

The mobile-reading test is simple: AirDrop the PDF to your phone (iOS) or email it to yourself and open from the phone (any platform). Read through it the way a recruiter would on the train. If anything is hard to read, fix it before submitting. The recruiter who has to zoom and pan to read your CV is not impressed by your design; they are annoyed by the friction.

Common PDF generation mistakes that break ATS parsing

Even with PDF as the right format choice, specific generation mistakes can still break ATS parsing. The avoidable ones:

Using design tools (Photoshop, InDesign, Illustrator) that default to image-PDF export. Switch to text-PDF export explicitly, or compose the CV in Word/Google Docs and only use design tools for visual assets
Building the CV in slides (PowerPoint, Keynote, Google Slides) and exporting to PDF. The slide-export pipeline often rasterises text or places it in unusual containers that ATS struggles with. Use document tools, not presentation tools
Multi-column layouts where the columns are implemented with text boxes rather than proper column formatting. The parser reads text-box content in the order the boxes were drawn, which is rarely the visual reading order. Result: scrambled content. Use Word's column feature or proper grid layout, not floating text boxes
Using tables for layout rather than data. Many ATS read table cells row-by-row, which destroys the reading order of a CV that uses tables to position labels and content side by side. Stick to flowing text and use tables only for actual tabular data
Headers and footers with text that the ATS may or may not extract — names, contact info, page numbers placed in document headers can be missed by some parsers. Put your name and contact details in the body of the document, top of page 1, not in a Word header field
Embedded images that contain text — a logo with a slogan, a section header rendered as an image because of design choice. The image text is invisible to the parser. Keep all important content as actual text
Hyperlinks that wrap the visible text in non-standard ways — some PDF exports treat hyperlinks as separate text objects that disrupt reading order. Test by selecting all text in the PDF (Cmd+A or Ctrl+A) and copying to a plain text editor. If the order is wrong or text is missing, the parser will have the same problem

The diagnostic for all of these: select all text in your PDF, copy, paste into a plain text editor, read the result. If the result is your CV content in the correct reading order, the ATS will parse it correctly. If the result is scrambled, missing sections, or full of weird characters, fix the source document before submitting. This 30-second test catches 95 % of PDF parsing issues.

Google Docs, Pages, LibreOffice — the export gotchas

If you are not using Microsoft Word, your tool's PDF export may have specific quirks worth knowing about:

Google Docs: 'File → Download → PDF Document.' Produces a clean text-PDF that ATS systems handle well. The font selection is more limited (Google Fonts only), but the export pipeline is reliable. Avoid 'Print → Save as PDF' as the browser may rasterise
Apple Pages: 'File → Export To → PDF.' Reliable text-PDF output. The Pages-default fonts (San Francisco, Helvetica, etc) embed correctly. Pages-specific design features (sidebars, infographic templates) sometimes export in ways that confuse ATS — stick to clean layouts
LibreOffice Writer: 'File → Export As → Export as PDF.' Produces excellent ATS-friendly PDFs. Make sure 'Use Tagged PDF' is enabled in the export options for best ATS compatibility. The 'Hybrid PDF' option creates a PDF that also contains the source document, which is not what you want for CV submission
Notion: Notion's PDF export has improved but historically has had issues with code blocks, embedded media and multi-column layouts. Test the output thoroughly if you are using Notion for your CV
Canva: Canva produces beautiful CVs but the PDF export defaults to image-heavy designs that often do not parse cleanly through ATS. Use 'PDF Standard' (not 'PDF Print') and avoid heavy image backgrounds. Test text-selection after export
Figma: Figma's PDF export is design-focused and often produces image-PDFs rather than text-PDFs. If you are building your CV in Figma, accept that you will need to also maintain a parallel Word or Google Docs version for ATS submissions and use the Figma version only for direct human-readable contexts (portfolios, design-team applications)
Old Word for Mac (versions before 2016): PDF export had reliability issues. If you are on legacy Office, update or use Google Docs

The pattern: document-first tools (Word, Google Docs, Pages, LibreOffice) produce reliable ATS-friendly PDFs. Design-first tools (Canva, Figma, InDesign, Photoshop) require deliberate effort to produce parseable output and often default to image-PDF. If you want a design-heavy CV, the safe approach is to maintain two versions: a design-tool version for visual contexts, a document-tool version for ATS-routed submissions. Many candidates who insist on Canva or Figma CVs and submit them to corporate ATS portals get screened out silently.

Password protection, watermarks, and other things that get you rejected

Some optional PDF features actively damage your application. Avoid all of these:

Password protection on the file. Recruiters will not email you for the password. They will skip you. There is no scenario in CV submission where password-protecting your PDF helps you; do not do it
Watermarks like 'DRAFT', 'CONFIDENTIAL', 'DO NOT DISTRIBUTE'. These are sometimes leftover from internal version-control workflows. The recruiter sees them as either unprofessional or as a confusing signal about whether you are really applying. Strip all watermarks before submitting
Document properties (author, title, subject, keywords) that contain previous companies, real names of people you copied content from, or revision history that reveals you reused another candidate's template. Check File → Properties (Word) or File → Info → Inspect Document before exporting. Strip personal metadata
Hidden text or comments left over from drafting. Track-changes markup, comments, and hidden formatting can sometimes survive the PDF export and appear when the recruiter views the document in certain readers. Accept all changes and remove all comments before exporting
Audio or video embeds. PDFs can contain media; CVs should not. Recruiters cannot or will not play the media, and the file becomes much larger
JavaScript or interactive form fields. Some PDF tools allow embedding interactive elements. CVs should not have them. Many ATS systems and corporate email filters quarantine PDFs containing JavaScript
Encryption beyond what your CV builder applies by default. If you have manually applied any encryption settings, remove them
Digital signatures from previous documents. If the PDF was generated by appending to a signed template, the signature can confuse the recruiter ('why is this signed by someone else?'). Re-export cleanly from the source

The pattern: anything that would make sense for a confidential business document or a contract is wrong for a CV. The CV is meant to be openable, readable, parseable and forwardable. Removing all the friction that confidential-document workflows introduce is the goal. Most candidates do not deliberately add these features but inherit them from templates or previous workflows. The audit takes 2 minutes; do it once and the cleaned-up source can be re-exported many times without re-checking.

The decision tree — what to send in which situation

Putting all the rules together into a single decision tree:

Job posting explicitly asks for Word: send Word. Match the exact extension if specified (.doc vs .docx). Do not question; do not substitute
Job posting explicitly asks for PDF: send PDF. Same rule, opposite format
Job posting silent on format, applying through a portal with file-type dropdown: choose PDF from the dropdown
Job posting silent on format, applying through a portal with no dropdown (uploads any file): send PDF
Job posting silent on format, applying via email: send PDF as attachment
Working through a recruitment agency: send Word to the agency (they will likely edit and forward as Word or repackage)
Submitting to a government agency, large enterprise HR portal, or other legacy-system context: send Word unless the portal explicitly accepts PDF
Submitting to a tech company, startup, modern enterprise, or design-led company: send PDF
Submitting to a creative or design role where the CV itself is part of your design portfolio: send PDF (the design quality is part of the candidate signal)
When in doubt for any case not covered above: send PDF. The cost of PDF in a Word-preferred context is usually low (most modern systems handle both); the cost of Word in a PDF-preferred context can be broken layout or unprofessional appearance

The summary rule: PDF is right 95 % of the time, with narrow exceptions that are usually flagged explicitly. The candidate who defaults to PDF and follows specific instructions when given them gets it right in essentially every situation. The candidate who agonises over each submission, sends Word out of fear of ATS, or substitutes formats against instructions creates problems that the right default would have avoided. Spend the energy on the CV content instead.

The complete CV-writing playbook: content beats format