PDF or DOCX for ATS: Which Resume Format Should You Use?

You are about to hit submit, and one last question is holding you up: should this resume go out as a PDF or a DOCX? It is a fair thing to pause on, and it is also the part of the application most people worry about more than they need to.

Here is the short version. Use the format the employer asks for. If they do not ask, a clean PDF is usually fine. And the single thing that matters more than the file extension is whether your resume has a simple, text-based structure that software can actually read. A beautiful file in the wrong shape fails. A plain file in the right shape sails through. The rest of this guide explains why, and how to get your file into that right shape from either Word or Google Docs.

If you want a decision in ten seconds, here it is:

• Follow the posting. If the job description or the upload field specifies PDF or DOCX, use exactly that. This overrules everything else below.
• If no format is specified, a clean text-based PDF is usually fine. Most modern ATS platforms read PDFs without trouble.
• Never upload a scanned image. A resume saved as a picture (or printed and scanned back in) has no readable text. This is the one genuine failure case, and it applies to PDF and DOCX alike.
• Layout beats extension. A single-column, standard-headings resume parses well in either format. A cluttered one parses badly in either format.

If that covers your situation, you are done. If you want to understand the reasoning so you can decide confidently next time, read on.

To choose well, it helps to know what each file type looks like to the software reading it.

What a DOCX is to an ATS

A DOCX is a Word document. Under the hood it is a structured package of text, styles, and layout instructions. For years this was considered the safest ATS format because the text content is stored in a fairly predictable, machine-readable way, and even older parsing engines handle it well. That reputation is largely deserved. The trade-off is that a DOCX can render differently on someone else's computer if they have different fonts or a different version of Word, so the recruiter may not see the exact spacing you designed.

What a PDF is to an ATS

A PDF is a fixed-layout document. It looks identical everywhere, which is why people like sending it. The important detail is that a PDF can store its content in one of two completely different ways. A text-based PDF contains a real, selectable text layer, and modern parsers read it cleanly. An image-based PDF contains only a picture of your resume with no text underneath, so a standard parser has little or nothing useful to extract.

Years ago, PDF support across ATS platforms was genuinely uneven, which is where the old "never send a PDF" advice came from. That advice is mostly outdated. Most modern systems read text-based PDFs reliably. For example, Greenhouse lists both .docx and .pdf as supported candidate uploads, and Lever says its parser can read Microsoft Word and Adobe PDF files. The risk now is not the PDF format itself. It is the image-only PDF, and the messy layout. Both of those are within your control.

If you take one warning from this article, take this one. The dangerous mistake is not choosing PDF over DOCX. It is submitting a resume that contains no readable text.

This happens more often than you would expect, usually like this:

• Print, then scan. Someone prints their resume, scans the paper back into a PDF, and uploads the scan. The result is a photograph of a document, not a document.
• Export as an image. A resume built in a design tool gets exported as a JPG or PNG, or as a PDF where every page is just an embedded image.
• Screenshot to PDF. Someone screenshots their resume and saves the image as a PDF to "lock it in."

In every case, the file looks perfect to a human and may be nearly blank to a parser. There is a thirty-second test that catches this problem: open your file and try to select the text with your cursor. If you can click, drag, and highlight individual words, you have a text layer and a parser can read it. If your cursor selects the whole page as one solid block, or selects nothing, your resume is an image. A standard resume parser has no underlying text to recover, and formatting cleanup will not create one.

The fix is simple: always generate your file by exporting it directly from the program you wrote it in, never by scanning or screenshotting. The next section shows exactly how.

Assuming both your files are clean and text-based, here is how to make the call.

Choose DOCX when

• The employer asks for it. Always. If the posting says Word document, send a Word document.
• You are applying through an older or unusual system. Some smaller companies, staffing agencies, and government portals run older software. DOCX is the more universally understood format, so it can be marginally safer when you have no idea what is on the other end.
• A recruiter will be editing your resume. Staffing agencies sometimes reformat candidate resumes onto their own template. An editable DOCX makes that easier, which can work in your favor.

Choose PDF when

• The employer asks for it, or the upload field accepts it without a stated preference.
• You want your layout to stay exactly as designed. A PDF looks the same on every screen, so spacing and alignment will not shift on the recruiter's computer.
• You are applying through a modern ATS. Most current platforms handle text-based PDFs well, so the consistency of PDF comes with little downside.

If the posting is silent and you still cannot decide, default to a clean text-based PDF. It is a safe, common choice. The marginal extra safety of DOCX only matters for genuinely old systems, and even then a clean PDF is rarely the thing that sinks an application.

Whichever format you choose, the goal is the same: a real document with a real text layer, exported straight from your editor. Here is how to do that properly.

From Microsoft Word

• For a PDF: go to File, then Save As (or Export), and pick PDF as the file type. Avoid the "Print to PDF" route when your source is anything other than a normal editable document, because printing a scanned or image-based page produces an image-only PDF.
• For a DOCX: simply save in the default .docx format. Save As, and confirm the file type is "Word Document (*.docx)" rather than an older .doc or a template.

From Google Docs

• For a PDF: go to File, then Download, then "PDF Document (.pdf)." For a normal text document, Google Docs exports a text-based PDF this way.
• For a DOCX: go to File, then Download, then "Microsoft Word (.docx)."

Two habits keep these exports safe. First, never export from a scanned page or a screenshot, because no export setting can add a text layer that was never there. Second, use standard fonts (Calibri, Arial, Times New Roman, Helvetica, Georgia). Standard fonts embed cleanly in a PDF and avoid character substitution problems. Once your file is exported, take a moment to open it and run the cursor selection test from the previous section before you upload.

Here is the part most format debates miss. You can pick the "perfect" extension and still get a poor parse, because the thing parsers struggle with is structure, not file type.

A resume that reads cleanly in either PDF or DOCX usually shares the same handful of traits:

• A single-column layout. Multi-column designs and sidebars often get scrambled when a parser flattens the page into a single stream of text. One column reading top to bottom is the safest structure.
• Standard section headings. Use predictable names like Work Experience, Education, and Skills so the software can sort your information into the right buckets.
• Standard fonts. Common, widely available fonts embed and render reliably across systems.
• Contact info in the body. Put your name, email, and phone number in the main text of the page, not in the document header or footer. Many parsers skip header and footer regions entirely.

There is a quick way to see what a parser sees: select all the text in your resume, paste it into a plain text editor, and read it top to bottom. If it comes out in a sensible order with nothing missing, your structure is sound. For the full step-by-step version of that check, see our guide on how to check if your resume is ATS-friendly.

If you would rather not eyeball it yourself, our free ATS checker reads your resume the way parsing software does and flags structural problems like multi-column layouts, missing text layers, and headers that hide your contact details. It runs entirely in your browser, with no signup, and your resume never leaves your device. It is a fast way to confirm your file is in good shape regardless of which extension you picked.

So, PDF or DOCX? Follow the employer's instructions first, every time. If the posting does not specify, a clean, text-based PDF is usually fine for modern ATS platforms, and DOCX is a reasonable, slightly more conservative choice for older or unfamiliar systems. Either way, you are choosing between two good options, not avoiding a disaster.

The real disaster, and the only one worth losing sleep over, is uploading a resume with no readable text or a layout that scrambles when it is parsed. Export your file directly from Word or Google Docs, confirm you can select the text with your cursor, keep the layout to a single clean column with standard headings, and the format question stops mattering much at all. Pick one, make sure it is clean, and submit with confidence.