You finished your CV, you are about to hit send, and a small doubt stops you: PDF or Word? It feels minor, but the wrong choice can quietly break your layout or trip up the software that reads your application first. Here is how to make the call without overthinking it.
Read the job post first
Before weighing any pros and cons, check what the employer asked for. Plenty of listings specify a format outright, and recruiters notice when you ignore it. If the post says "send your CV as a Word document" or the upload form only accepts .docx, that is your answer. Following the instruction is itself a small signal that you read carefully.
When no format is requested, the decision is yours, and that is where the real trade-offs come in.
What PDF does well
A PDF locks your formatting. The fonts, spacing, columns, and bullet alignment look the same on the recruiter's screen as they did on yours, whether they open it on a Mac, a phone, or an old office laptop. That reliability is the main reason PDF has become the default for most direct applications.
PDFs also feel finished. There is no blinking cursor, no "track changes" residue, no risk that someone accidentally edits a line. For a document meant to represent you, that polish matters.
The catch: some older or poorly configured applicant tracking systems still struggle to parse certain PDFs, especially ones exported as images or built with heavy design tools. A text-based PDF from Word, Google Docs, or a standard CV builder parses fine almost everywhere. A PDF that is secretly a flattened image does not.
When Word is the safer bet
Word files stay editable, and sometimes that is exactly what the other side wants. Recruitment agencies in particular often ask for .docx because they reformat your CV, strip their competitor's branding, or insert their own header before passing it to the client. A locked PDF gets in their way.
Word also remains the most universally parseable format for older ATS software. If a listing runs through an obviously dated system, or you simply cannot tell, a clean .docx is the low-risk choice. The downside is that your careful layout can shift on a machine with different fonts or a different Word version. Keep the design simple and that risk shrinks.
If you want a deeper look at how parsing actually works across formats, our breakdown of PDF vs Word for ATS goes one layer down.
A simple rule that covers most cases
- The job post names a format: send that, no debate.
- A recruitment agency is handling it: send Word unless told otherwise.
- Direct application, no instructions: send a text-based PDF.
- You are unsure and cannot ask: Word is the conservative fallback.
Whatever you send, name the file like a professional: Firstname-Lastname-CV.pdf, not cv_final_v3_REAL.docx. The filename is the first thing a recruiter sees in their inbox.
Export it cleanly, whichever format you pick
The format only protects you if the file underneath is clean. Build your CV in a tool that produces real, selectable text rather than an image. If you are pulling your experience together from a LinkedIn profile, Postulit turns that into a properly structured CV you can export either way, so the format choice stays a choice and never a repair job.
The takeaway: there is no universally "correct" format, only the right one for the situation in front of you. Read the post, consider who opens the file next, and pick accordingly. Spend the energy you save on the content instead, because that is what actually gets you the interview.