Should I submit my CV as PDF or Word if the posting doesn't say?

Use PDF. It keeps your formatting intact across every device and recruiter, and modern ATS platforms like Workday, Greenhouse, and iCIMS parse text-based PDFs reliably. Only switch to Word if the posting names it or your layout is heavily designed.

Can an ATS actually read a PDF?

Yes, as long as it's a text-based PDF—one exported from Word, Google Docs, or a resume builder, not a scanned image. Image-based PDFs contain no selectable text, so no ATS on the market can extract anything from them.

Why do some job postings ask for a Word document specifically?

Usually because a recruiter or agency wants an editable file—to strip contact details before forwarding it to a client, apply a company template, or work with an older internal system. When a posting names Word, that instruction overrides the general PDF default.

Will a two-column CV in PDF format still get parsed correctly?

Often not cleanly. Some parsers read across columns left to right instead of down each column, scrambling dates and job titles. If your CV uses columns, tables, or text boxes, a single-column Word version is the safer bet for ATS-heavy applications.

How do I convert my CV to PDF without breaking the ATS-readable text?

Export directly from Word or Google Docs using File > Save As / Download as PDF rather than printing to PDF or scanning. This keeps the text layer selectable. Then open the PDF and try to select and copy a paragraph—if that works, an ATS can read it too.

CV PDF or Word Format: Which One Actually Passes ATS?

Listen to this article

You're at the upload screen. The job posting says nothing about file type, your CV is finished, and now you're staring at two options — save as PDF, or leave it as a Word document — wondering if picking wrong could get your application filtered out before a human ever sees it. This is a smaller decision than it feels like, but it's not a nothing decision either, and most guides answer it with a rule that skips the reasoning: "always use PDF unless told otherwise." That's usually right. It's just not the whole answer.

Here's the actual one, including the two situations where it flips.

The Short Answer: PDF, With Two Exceptions

Person staring at a screen looking uncertain about which button to click — via GIPHY

Submit your CV as a PDF by default. Modern applicant tracking systems — Workday, Greenhouse, Lever, iCIMS, the platforms that sit behind most mid-size and large employers' careers pages — parse text-based PDFs without trouble, and PDF guarantees the recruiter sees the exact layout you designed, on any device, in any viewer.

There are two situations where you should switch to Word instead:

The job posting or application portal explicitly asks for a Word document (.doc or .docx).
Your CV relies on multi-column layouts, tables, text boxes, headers/footers with contact details, or embedded graphics that a parser might not read in the right order.

Outside those two cases, PDF is the safer choice. Neither format is inherently "more ATS-friendly" in the way a lot of CV advice implies — the format matters less than what's inside it, which is the part worth understanding before you pick.

Why PDF Is the Safer Default

A PDF exported directly from Word, Google Docs, or a CV builder is a text-based PDF: the words are stored as selectable, searchable text, not as an image. That's the file an ATS actually needs — it can extract your job titles, dates, and skills exactly as they appear, because the text is there to extract.

The other reason PDF wins by default has nothing to do with parsing and everything to do with the human who eventually opens the file. A CV built with any care over spacing, alignment, or a subtle divider line can shift when opened in a different version of Word, a different font substitution, or a different operating system. A PDF looks the same everywhere. If a recruiter opens your file on a phone during a commute, you want it to look like the file you approved, not a version where a table row wrapped wrong and pushed your most recent job off the page.

This is also the format assumption behind most modern ATS-friendly formatting advice — clean single-column structure, standard section headers, no graphics doing the work of information. If you haven't audited your CV against that baseline, the ATS-friendly CV format guide covers the formatting mistakes that quietly break parsing regardless of file type.

Exception One: When the Job Posting Asks for Word

If a posting says "submit as .docx" or the application portal only accepts Word files, that instruction overrides the general PDF default — every time, no exceptions of your own.

There are a few real reasons employers do this, and none of them are a trap:

Older or internal ATS platforms that were configured years ago and were never updated to handle PDFs cleanly, particularly in the public sector and some larger legacy organizations.
Staffing and recruitment agencies often want an editable file so they can remove your contact details, reformat the document into their own template, or add a cover sheet before forwarding it to their client — a common practice noted by resume-industry sites like Jobscan.
Internal HR teams that keep a standard document template and merge candidate information into it for record-keeping.

None of these mean your CV will be judged more harshly for being editable. It's a workflow request, not a formatting test. Ignoring it, on the other hand, is a formatting test you can fail for no good reason — some portals will simply reject a PDF upload outright, and others will accept it but hand a broken Word conversion to whoever reviews it next. When in doubt about what a posting is actually asking for, this is one of the rare cases in a job search where following the instruction to the letter beats optimizing around it.

Exception Two: When Your CV Design Breaks the Parser

The second exception has nothing to do with what the employer requested and everything to do with what you built. A heavily designed CV — the kind with a sidebar for skills, a two-column body, icons next to section headers, a photo, or a colored background block — can produce a PDF that looks perfect to your eye and unreadable to a parser.

The specific failure modes are worth knowing, because they explain why "just save it as PDF" isn't universally safe advice:

Multi-column layouts are sometimes read left-to-right across the whole line instead of top-to-bottom within each column, which interleaves your job history with your skills list into nonsense.
Tables used for layout (rather than for genuinely tabular data) can lose their reading order entirely, scrambling dates, titles, and companies.
Text boxes are sometimes skipped by parsers completely — meaning a phone number or job title placed in one can simply vanish from the extracted text.
Headers and footers holding contact information are inconsistently read; some systems ignore them outright.
Scanned or image-based PDFs — a photograph or scan of a printed page — contain no selectable text at all, so no ATS on the market can read a word of them, regardless of format.

If your CV design falls into any of these patterns, converting it to a clean, single-column Word document (or rebuilding it in one) is the more reliable move for ATS-heavy applications — not because Word parses better than PDF in principle, but because a well-structured Word file is less likely to carry the layout tricks that cause the problem in the first place. If you're deciding between layout styles from the start, single-column versus two-column CV layouts is worth reading before you build the design, not after a rejection makes you suspicious of it.

What Actually Happens When an ATS Parses Your File

It helps to know what "parsing" means in practice, because the term gets thrown around as if ATS software is reading your CV the way a person does. It isn't. An ATS extracts your file's text layer and tries to sort it into fields — name, contact info, job titles, dates, education, skills — usually to populate a searchable candidate database and, in some systems, to generate a match score against the job description's keywords.

That process depends entirely on the text being extractable and roughly in a predictable order. A resume file format that an ATS parses cleanly is one with real, selectable text, standard section headings ("Experience," "Education," "Skills" — not creative renamings), and a linear structure a machine can walk through the way a person reads a page: top to bottom, one column.

This is also why file type alone was never really the variable that mattered. Two PDFs can behave completely differently depending on how they were made — one exported cleanly from a word processor, one flattened from a scanned image — and two Word documents can behave differently depending on whether the layout uses simple paragraphs or a table-based design borrowed from a template. If you want the deeper mechanics of how these systems rank and filter candidates, the ATS CV guide goes further into how scoring actually works.

How to Convert Your CV to PDF for ATS Without Breaking It

If you've decided PDF is right for this application, the way you create the file matters as much as the choice itself.

Export directly from your source document rather than printing to PDF or using a phone-scanning app. In Word, that's File > Save As > PDF, or File > Export. In Google Docs, it's File > Download > PDF Document. Both preserve the underlying text layer as selectable text, which is what keeps the file machine-readable.

Before you submit, run one quick check: open the PDF and try to select and copy a line of text with your cursor. If it highlights and copies normally, the text layer is intact and a parser can read it. If nothing selects — if it behaves like a photograph — you have an image-based PDF, and no ATS will extract a single word from it. That single check catches the most common way people accidentally submit an unreadable file without realizing it.

Also worth doing: name the file something a recruiter can identify at a glance in a folder of forty other applicants — your name and "CV," not "Document1" or "Final_v3_edited." It's a small thing, but it's one more place a careless default costs you nothing to fix.

A Simple Decision Checklist

When you're not sure which format to submit, this covers the situations you'll actually run into:

Does the posting or portal name a specific file type? Follow it exactly — this overrides every other consideration.
Is your CV a straightforward, single-column layout with standard headings? Submit as PDF, exported directly from your source file.
Does your CV use columns, tables, text boxes, or heavy graphic design? Either simplify the layout, or submit as Word so the structure survives extraction.
Are you emailing your CV directly to a person rather than uploading it to a system? PDF, so it displays identically regardless of what software they open it in.
Not sure if your file is genuinely readable either way? Open it and try to select the text. If you can't select it, no format choice fixes that — you need to rebuild it from a real text source.

None of this is about outsmarting software. It's about making sure the CV you worked on actually reaches the recruiter in the shape you intended, instead of arriving as a scrambled version of itself because of a formatting choice nobody explained to you.

Format is only ever the delivery mechanism, though. A cleanly parsed CV that says nothing distinctive about you still lands flat once it's in front of a person. If you've fixed the file type question and you're still not landing interviews, that's usually a content problem, not a parsing one — and it's worth a second, human pair of eyes before you send out another round. Kaeros's free CV review is a real person reading your CV and telling you plainly what's working, what raises doubts, and what to fix first — no account needed, no cost, and no pressure if it's already in good shape. If you want a faster first pass on your own, the CV mistake checker flags common issues before you submit.