You have rewritten your resume, tailored it to the job, and now you are stuck on one small, nagging question: should you send it as a PDF or a Word file, and could the wrong choice quietly get you filtered out before a human ever sees it? It is a fair worry, because the file format really can decide whether an applicant tracking system reads your resume cleanly or turns it into scrambled text. Here is the honest, current answer for 2026, plus exactly how to make sure the format you pick actually works.
The short answer
For most people, the best resume format for ATS in 2026 is a text-based PDF. It keeps your layout exactly as you designed it for the human who eventually reads it, and every major modern applicant tracking system can parse a clean, text-based PDF without much trouble.
There is one rule that overrides everything else: if the application tells you what it wants, follow it. When a form says "Word documents only" or "upload a .docx," give it a .docx. The employer's instructions beat any general advice, including ours.
One honest caveat worth saying up front: there are hundreds of ATS platforms, and they behave differently. No article and no tool can perfectly replicate a specific company's system or promise you will pass it. What you can do is avoid the file-format mistakes that break parsing almost everywhere, and that is most of the battle.
PDF vs Word: what actually changes for the parser
Both PDF and Word (.docx) are well supported by modern applicant tracking systems, and a clean file in either format will usually parse fine. The difference is in the tradeoffs.
- PDF locks your layout in place. What you see is what the recruiter sees, with no fonts shifting or bullets sliding around on their screen. A text-based PDF is fully readable by current parsers.
- Word (.docx) is editable, which some systems and recruiters prefer because they can re-flow or annotate it. It is also the safest fallback for older or unusual systems.
The old advice that "Word is always safer" comes from an era when many parsers genuinely choked on PDFs. For a clean, text-based PDF, that is largely outdated in 2026. That said, a handful of older or misconfigured systems still handle Word more predictably, so if you have no other information and the layout is simple, .docx is a reasonable safe choice too. If you want to understand what happens after you upload either file, our guide on what an ATS actually reads from your resume walks through it.
The formats to avoid
Some file types cause problems often enough that you should just rule them out unless an employer specifically requests them.
- .doc (the old Word format). Use the modern .docx instead.
- .pages (Apple Pages native). Many systems cannot open it at all. Export to PDF or Word first.
- .txt (plain text). It is technically the most parseable format, but it strips all formatting and looks bare to a human reader. Only use it if the application explicitly asks for it.
- .rtf (rich text). Support is inconsistent and unpredictable.
- Image files (.jpg, .png) or a resume built and exported as a picture. A parser sees no text at all, just an image.
- A Google Docs share link. Upload an actual file, do not paste a link, unless the form asks for one.
The trap that makes format almost irrelevant
Here is the mistake that sinks more resumes than PDF-versus-Word ever will: sending an image of a resume instead of real text.
A PDF can contain two very different things. It can hold real, selectable text that a parser reads word for word. Or it can hold a flat picture of text, which happens when you scan a printed page, screenshot your resume, or export a design as an image. To a parser, that second version is close to blank. Some systems try optical character recognition to guess at the words, but that is unreliable and you do not want to bet your application on it.
There is a five-second test. Open your PDF, then try to click and drag your cursor to highlight a line of text. If the words highlight like text in a document, you are good. If your cursor just draws a box over a picture and nothing selects, it is an image, and you need to export it again as real text.
This matters most if you build your resume in a design tool. Some of them can export heavy graphics or flatten text into an image. Keep the layout simple, keep the text as text, and always run the highlight test before you send.
How to export a clean file
Getting a proper text-based file is usually one menu click away.
- From Word: use File, then Save As or Export, and choose PDF. Do not "print to image" or export as a picture.
- From Google Docs: use File, then Download, then either PDF Document (.pdf) or Microsoft Word (.docx).
- From Apple Pages: use File, then Export To, then PDF or Word.
While you are at it, give the file a clear name like Firstname-Lastname-Resume.pdf. It helps a recruiter find you later, and it beats sending something called "resume-final-v7(2).pdf." Avoid odd symbols and spaces where you can.
Format is only half the job. A single-column layout, standard section headings like Experience and Education, and real selectable text will parse well in either PDF or Word. Fancy tables, text boxes, and multi-column designs are the usual reason a good resume comes out garbled, and switching file types will not fix a layout problem. Our roundup of resume red flags that get auto-rejected covers the layout traps in more detail.
A quick real example
Maya, a marketing coordinator, built a beautiful resume in a design app with two columns and a sidebar of skill icons. She exported it as a PDF and applied to a dozen roles with no replies. When she finally checked the parsed output, her job titles were interleaved with her skills, and half her sidebar had vanished, because the parser read the columns in the wrong order and could not decode the icons.
She did not need a new file format. She rebuilt the same content as a single-column layout with plain text headings, exported it again as a text-based PDF, and ran the highlight test to confirm the text was selectable. Same PDF format, same experience, completely different result on the parser's side. The lesson: the format was never her real problem, the layout was.
Check your file before you send it
You do not have to guess whether your file will read correctly. Do a quick copy-paste test yourself: open your resume, select all the text, paste it into a plain text editor, and read it top to bottom. If your name, titles, and bullets come out in a sensible order, a parser will likely read it the same way. If it is jumbled, that is your warning.
If you want to see it the way the software does, Bounce's free Beat the Bots scan at careerbounce.io shows you the literal text an ATS-style parser pulls from your file, the X-Ray view. You find out in a couple of minutes whether your PDF is text or an image, and whether your sections survived the parse, before a recruiter ever opens it.
And if you would rather not fight the layout at all, Bounce Studio builds an ATS-clean resume for you using only your real experience, then tailors it to each job. It is verified to never invent skills or tools you do not have, so the resume that passes the parser is one you can defend, line by line, in the interview. For the bigger picture on parsers, see our guide on how to beat applicant tracking systems.
The 30-second file-format checklist
Before you hit submit, run through this:
- Did the application specify a format? If yes, use that. If no, default to a text-based PDF.
- Can you highlight the text in your PDF with your cursor? If not, re-export it as real text.
- Is it a .docx, not an old .doc, if you are sending Word?
- Did you avoid .pages, image files, and share links?
- Is the layout a single column with standard headings and no image-only text?
- Is the filename clean and human-readable?
Get those six right and your file format will do its job, which is simply to get your real, honest experience in front of the person who decides. Everyone bounces back, and a clean file is one less thing standing in your way.