Should Your CV Be a PDF or a Word File?

PDF or Word is one of the few CV questions with a short, defensible answer, and it still gets argued about because the advice on both sides is a decade out of date.

The short version: send a text based PDF unless the advert or the recruiter asks for Word. That covers the overwhelming majority of applications. The rest of this article is why, when the exception applies, and the file problems that actually cost people interviews.

Why PDF is the default

Three reasons, in order of importance.

It looks the same everywhere. A Word document reflows on the recipient's machine according to their fonts, their version of Word and their page settings. Your carefully set two pages become two and a half, a heading lands alone at the bottom of a page, and your date column drifts out of alignment. A PDF is fixed. What you exported is what they open.

Nobody can edit it accidentally. Word documents pick up stray keystrokes, and worse, they carry tracked changes and comments if you forgot to accept them. Sending a CV with a visible comment from a friend saying "maybe drop this job" is a real thing that happens.

It is parsed reliably. This was a genuine concern around fifteen years ago and has not been for a long time. Text based PDFs are read accurately by mainstream systems, as covered in what an applicant tracking system actually is.

There is a fourth, smaller reason: a Word file carries metadata, including the document author, the company name from whoever's licence created it, and sometimes the editing history. It rarely matters, and occasionally it is awkward, for example when the author field still shows a former colleague's name.

When Word is genuinely right

Three cases, and they are worth taking seriously rather than treating as exceptions to argue with.

The advert or portal asks for it. Follow the instruction. There is no advantage in demonstrating independent judgement about file formats at the application stage.

A recruitment agency asks for it. This is the most common legitimate case. Agencies frequently rebrand CVs onto their own template before sending them to clients, removing your contact details so the client cannot approach you directly. They need an editable file to do that, and giving them a PDF creates work that occasionally results in a worse version of your CV, retyped by someone in a hurry.

An internal application system requires .doc or .docx. Some older enterprise portals still do. Rare, but it happens, and the upload will simply reject anything else.

Outside these three, PDF.

The file types to avoid

A PDF that is really a scan or a photo. This is the single worst thing you can send. It contains no text at all, so it parses to an empty record, and a candidate with no name and no phone number in the database is unreachable. If you have only a printed copy of your CV, retype it rather than scanning it.

A file exported as flattened artwork from a design tool. Same problem, different cause. Some export settings convert all text to outlines, which looks identical on screen and contains zero readable text. Always check by selecting the text.

Pages, ODT and other native formats. Not because they are bad, but because the recipient may not be able to open them. Export to PDF from whatever you use.

Google Docs share links. A link is not an attachment. It may require sign in, it can break, permissions can be wrong, and it does not go into the employer's system as a file. Download and attach.

Anything zipped. A ZIP file containing your CV adds a step and occasionally trips a mail filter. Attach the document directly.

Very large files. A CV should be well under 1MB. If yours is 8MB, it contains an uncompressed photo or an embedded image of the whole page. Some portals reject files over a size limit, and a rejected upload at 11pm is how applications get abandoned.

Checking your export actually worked

Two minutes, and it catches the failures that matter.

Open the PDF and try to select your own name with the cursor. If the text highlights, you have a text based PDF. If nothing selects, you have an image and it needs redoing.

Copy all the text and paste it into a plain text editor. Read what comes out. This is roughly what a parser sees, and it exposes column problems, missing headers and dropped contact details at the same time. The full test is described in the formatting that actually breaks an ATS.

Check the page count. Exports sometimes add a blank final page, usually from a stray paragraph mark at the end of the document. It looks careless and it is invisible until you look.

Open it on a phone. A large share of first looks now happen on a phone, and this is where a cramped layout or pale grey text becomes obvious.

How to export properly

From Word: use Save As or Export and choose PDF, rather than printing to PDF, which on some setups rasterises the page. If there is an option for document structure or accessibility tags, leave it on.

From Google Docs: File, Download, PDF Document. This produces a clean text based file.

From Pages or LibreOffice: export to PDF rather than saving in the native format, and check the text is selectable afterwards.

From a design tool: make sure text is exported as text rather than outlines, and export at a sensible resolution rather than print quality with embedded high resolution images.

One setting worth knowing: PDF/A is an archival format some systems request. It is fine for parsing, and you only need it if asked.

What to call the file

A small thing that costs nothing and helps a real person.

Use a clear, predictable pattern: `firstname-lastname-cv.pdf`. If you are applying to a specific role and want to be helpful, `firstname-lastname-cv-marketing-manager.pdf` also works.

Avoid spaces, accented characters and version markers. A recruiter downloading forty files into one folder ends up with thirty called `CV.pdf` and yours should not be one of them. And `Jane Smith CV final v3 (2).pdf` says something about your process that you did not intend to say.

The file name has no effect on parsing, so this is purely for the human. That is reason enough.

Two files, one content

The practical setup that solves most of this.

Keep your CV in one editable master document, in Word or Google Docs. Export a PDF from it for each application. When an agency asks for Word, send the master.

The mistake to avoid is maintaining two separate documents that drift apart. Six months later your Word version has an updated job title and your PDF does not, and you send whichever one you find first. One source, exported as needed.

If you keep separate versions for different markets or languages, distinguish them in the file name rather than in your memory.

Email versus upload

Two contexts with slightly different rules.

When uploading to a portal, follow the accepted formats listed by the form, keep the file small, and check the parsed preview if the system shows you one. That preview screen is the most useful feedback in the whole process and most candidates click past it.

When emailing directly, attach the PDF rather than pasting the CV into the body of the email, which loses formatting entirely. Write a short covering note in the email body itself, name the file properly, and check the attachment is actually attached before sending, which remains one of the most common self inflicted wounds in job hunting.

Do not send both a PDF and a Word version of the same CV. Most systems either overwrite the first or store one and never open it, and any small difference between the two reads as carelessness.

Why the old advice persists

Worth a paragraph, because understanding where "never send a PDF" came from explains why you still hear it.

In the late 2000s and early 2010s, parsing was genuinely worse and PDF support was genuinely patchy. Some systems of that era handled Word reliably and PDFs badly, so the advice to send .doc was correct at the time. It was written down, repeated, and then never re-examined, which is how most CV folklore forms.

Two things changed. Parsers improved substantially, and PDF became the default output of every word processor and design tool, which made supporting it non optional for vendors. Today the direction has effectively reversed: PDF is the safer choice, and the remaining Word requests come from agencies who want to edit rather than from systems that cannot read.

This is a useful example of a wider pattern discussed in ATS myths: a lot of confident CV advice was accurate once and simply aged out without anyone announcing it.

Word specific traps

If you are sending Word because you were asked to, four things are worth checking first.

Tracked changes and comments. Turn off tracking, accept all changes, and delete every comment. Then check again, because Word sometimes displays a clean view of a document that still contains markup.

Document properties. File, Info, Properties shows the author name and company. If your CV was started from a template or a friend's file, this field may say something you did not intend.

Unusual fonts. If the recipient does not have your typeface, the document reflows. Stick to widely installed fonts when sending Word, which is one of the few contexts where font choice genuinely matters, as covered in CV fonts and layout.

Compatibility mode. Documents created in very old versions sometimes open in compatibility mode and render slightly differently. Save a fresh copy as .docx before sending.

A checklist before you hit send

Six items, about three minutes in total, and they catch nearly every file level failure.

The text in the PDF is selectable. The file is under 1MB. The file name is your name plus "cv", with no spaces or version numbers. There is no blank page at the end. It opens correctly on a phone. And the attachment is actually attached to the email.

That last one is not a joke. It is among the most common errors in job applications, and it produces a follow up email that starts with an apology at exactly the moment you wanted to look organised.

Frequently asked questions

Is PDF really safe for applicant tracking systems?

Yes, for text based PDFs, and it has been for many years. The only PDF that fails is one containing no text, such as a scan or an exported image.

The advert does not say which format. What do I send?

PDF. It is the safer default and it preserves your layout for the human reader.

Should I password protect my CV?

No. A password protected file cannot be parsed, may not open on the recipient's system, and creates friction at exactly the moment you want none.

Does the file size matter?

Yes, at the extremes. Keep it under 1MB. Large files come from uncompressed photos and occasionally get rejected by upload limits.

Can I send a link to an online CV instead?

Only in addition, never instead. A link may not open, will not enter the employer's system as a document, and cannot be forwarded internally the way an attachment can.

What about the CV I upload to a job board profile?

Same rules, with one addition: remember to update it. A file uploaded eighteen months ago and forgotten is the version employers are actually seeing, regardless of how current your desktop copy is.

Confirm your exported file is readable

The one file problem with a total cost is a PDF that contains no text, because it produces an empty record and there is no recovery from it. CvLaunch reads your file and shows you what was extracted, which tells you immediately whether your export worked and whether your name, dates and contact details survived it. It takes a few seconds, it is free, and there is no sign up.

What happens to your file after you upload it

A short note, because it clarifies several of the decisions above.

The file you upload becomes two things: a parsed record and a stored original attachment. The record is what gets searched and what fills the columns in a list view. The original is what gets opened when someone decides to look. Your format decision therefore serves both audiences at once: PDF preserves the original for the human, and being text based keeps the record populated.

This also explains why uploading a second file to the same application does not help. The system usually either overwrites the first or stores the second as an attachment nobody opens. Two versions do not create two records, they just make it unclear which one is current.

Finally, your file stays there. Apply to the same company six months later and the old file is still on your record, and a recruiter can see both side by side. That is a practical reason to keep versions consistent rather than letting an old upload contradict a new one.