Should you send your resume as PDF or Word?

PDF looks better. Word parses better. The right choice depends on who reads your resume first: a machine, or a person.

Table of contents
Tailor my resume →
A sheet of paper and a sealed cream envelope resting on a weathered wooden fence post, in a meadow of blue-and-white wildflowers with rolling green hills under warm early sunlight

This is one of the few resume questions with a genuinely useful short answer, and then a longer answer worth knowing. The short answer: submit .docx to online application portals, unless the posting specifically asks for a PDF. Send PDF when a recruiter asks you to email your resume, or when formatting matters more than parsing.

The longer answer is about what happens between you pressing "submit" and a human seeing your name. On most online portals, the first reader is not a person. It is an applicant tracking system that has to extract your text — your job titles, your dates, your skills — from whatever file you uploaded. Some files make that job easy. Some make it fail quietly, and you never find out.

The short answer, by situation

SituationSend thisWhy
Online application portal (ATS).docxThe format parsers were built around; the lowest risk of extraction errors
Posting explicitly says "upload PDF"PDFFollow the instruction; a text-based PDF from Word or Google Docs parses fine
Emailing a recruiter directlyPDFYour formatting arrives exactly as designed, on any device
Networking, career fairs, printingPDFLooks identical everywhere; nothing shifts between computers

That is the whole decision in practice. The rest of this post explains the reasoning, so you can handle the edge cases with confidence instead of guessing.

Why .docx is the safer default for portals

Most applicant tracking systems were designed around Microsoft Word files. A .docx file carries your text in a structured, predictable way: paragraphs, headings, and tables that the parser can read directly. PDF was built for something else entirely. It was designed to make a page look identical everywhere it is printed or opened, which means it describes where every glyph sits on the page, not what the document means.

Modern ATS platforms handle text-based PDFs reasonably well, but not all of them, and older systems in particular can stumble: misreading tables, dropping fonts that were not embedded, or scrambling the order of text pulled from columns and text boxes. A resume that looked perfect to you can arrive at the recruiter as a jumbled paragraph, with your skills section merged into your contact line and your dates attached to the wrong jobs.

This is not a reason to fear PDF. It is a reason to default to .docx when the portal does not specify, because the downside is invisible: if the parser misreads your file, nobody tells you. You just do not hear back.

What actually breaks in a PDF

Not all PDFs are equal. A text-based PDF exported from Word or Google Docs is usually parsed fine. The PDFs that cause real damage are:

  1. Scanned or image PDFs. If your resume is a photo of a page, the parser reads zero words. Some systems run OCR; many do not. Never submit a scan.
  2. Design-tool exports. Resumes built in Canva, InDesign, or similar tools look polished, but they are design files, not documents. The exported PDF often carries graphics, text boxes, and non-standard text rendering that scramble extraction. Gorgeous to a human, near-empty to a parser.
  3. Fonts that are not embedded. If your font is not installed on the parsing machine and was not embedded in the file, characters can render as blanks or gibberish. Stick to standard fonts: Arial, Calibri, Cambria, Garamond, Georgia, Helvetica, Times New Roman, Trebuchet MS.
  4. Layout features that confuse reading order. Multi-column layouts, tables, text boxes, headers and footers, graphics, icons, and decorative bullets can all come out in the wrong order. This is the same reason a single-column layout survives parsing best: the reading order is the writing order.

If you are submitting a PDF to a portal, it should be a plain, text-based export from a word processor. Anything fancier belongs in the envelope you hand to a person, not the file you feed to a machine.

The 60-second test that settles it

You do not need special software to check whether your file will parse. Open it, select all the text, copy it, and paste it into a plain-text editor like Notepad. Then read what comes out.

What to look for

Passes: the text reads top to bottom in the same order as your resume, every section is there, and nothing is merged into one wall of text.

Fails: text arrives jumbled or out of order, characters are missing or replaced with symbols, or sections appear in a scrambled sequence.

If it fails, the parser will see the same mess you see. Rebuild the resume in Word or Google Docs with a simple layout, and submit the .docx.

Run this test on the actual file you plan to upload, not on a different version of it. The test takes a minute and catches the exact failure that costs people interviews silently.

When PDF is the right choice

The parser argument only matters when a parser is involved. Plenty of situations have no parser at all, and there PDF's strengths take over:

  1. A recruiter asks you to email your resume. They will open it on a phone, a tablet, or a laptop with a different word processor. PDF is the only format that looks identical everywhere. A .docx can reflow, substitute fonts, and shift your careful layout.
  2. The posting says "PDF". Always follow the explicit instruction. A text-based PDF from Word or Google Docs is the right file here, not a design-tool export.
  3. Printing, career fairs, networking. PDF prints exactly as designed. This is the format's home ground.

Note the asymmetry: PDF's advantage is visible (you see the formatting hold), while .docx's advantage is invisible (the parser reads it cleanly). That is why people default to PDF even for portals — the PDF looks better, and the parsing failure never announces itself.

Get the filename and the export right

Two details people overlook. First, the filename. Some systems show the recruiter the filename of your attachment. Save it as Firstname-Lastname-Resume-2026.docx. "Final_v3_updated(2).docx" is not the first impression you want, and it is a surprisingly common one.

Second, the export. If you need a PDF, export it from Word or Google Docs — File, then Export or Download as PDF. Do not export from a design tool and do not "print to PDF" from a browser tab of a web app unless you have run the 60-second test on the result. The tool that made the layout determines what the parser can read.

Keep both versions

The practical answer for most job seekers is to maintain two versions of the same resume: a .docx for online portals, and a PDF for humans. They should contain the same text. Update both when you change one, or you will eventually send the wrong vintage to the wrong audience.

This is also why the format question and the tailoring question are related. The file format decides whether your resume gets read at all; tailoring it to the posting decides whether it ranks once it is read. Format is the envelope. The content is the letter. Before you submit either version, run it through an ATS checker to confirm the skills and terms you care about are actually extracted — that is the machine-readable test of the letter inside the envelope.

One honest note: if you use Tailr, you do not have to rebuild either version by hand. Every tailored resume exports as a one-page PDF or an editable DOCX, so the portal version and the human version stay in sync. The free tier covers 10 tailored resumes a day, which is enough to keep both current across a normal application week. See pricing for the paid tiers.

The quick checklist

Before you submit, run through this list:

  1. Online portal with no format specified: .docx. Posting says PDF: PDF. Emailing a recruiter: PDF.
  2. The PDF, if you send one, is a text-based export from Word or Google Docs — never a scan, never a design-tool export.
  3. Standard fonts, single column, no tables, text boxes, headers, or footers.
  4. The 60-second select-all test reads clean and in order.
  5. Filename is Firstname-Lastname-Resume-2026, not a draft name.
  6. Both versions contain the same current text.
  7. Your ATS checker pass confirms the terms you care about are extracted.

The bottom line

The file format is not the star of your application, and that is exactly why it matters. It is plumbing. Get it right and nobody notices; get it wrong and your resume can be unreadable to the one reader that matters most, with no error message to tell you. Default to .docx for portals, use PDF for people, test the file you actually submit, and keep the content — the tailored, honest letter inside the envelope — as the thing you spend your real effort on.

Put this into practice.

Tailor your resume to a real posting in a few minutes — free, with managed AI.

Tailor my resume →