Do applicant tracking systems really reject PDFs?

Most modern ATS accept PDFs fine — the myth that "PDFs get auto-rejected" is largely outdated. The real risk is not the format but the formatting: an ATS parses your resume into structured text (name, contact, work history, skills), and if your PDF is hard to parse, fields come through garbled or empty, which can hurt how you rank or match. So the goal is not to avoid PDF; it is to make a PDF the parser can read cleanly. A well-structured PDF resume parses as well as a Word document. When a posting explicitly demands .docx, follow it, but otherwise a clean PDF is fine and preserves your formatting.

What is the single most important rule?

Use real, selectable text — never submit a resume that is an image. If you designed your resume in a graphics tool and exported it as a picture, or scanned a printout, the ATS sees a blank page because there is no text to parse, and you effectively submit nothing. Open your PDF and try to select the text with your cursor; if you cannot, it is an image and will fail. Everything else (columns, fonts, headings) is secondary to this: the resume must contain actual text. If yours is an image, recreate it as a text document and export a text-based PDF.

Why do multi-column resumes cause problems?

Because a parser reads the text in the order it is stored, and a two-column layout can be stored in a way that interleaves the columns — so your left-column skills get mixed into your right-column job descriptions, producing scrambled, low-quality parsed data. A single-column layout reads top-to-bottom in the natural order and parses cleanly. Designers love columns, but for ATS reliability a single column is far safer. If you want a two-column look for human readers, keep a single-column ATS-friendly version for online applications and use the designed version only when handing a resume to a person.

How should I handle fonts and headings?

Use standard, readable fonts and embed them so the PDF renders consistently — exotic decorative fonts can both parse poorly and render as substitutes. For headings, use the conventional section names ATS look for: "Work Experience" or "Experience", "Education", "Skills" — not clever alternatives like "Where I've Made an Impact", which a parser may not recognise as the experience section. Put real text dates and job titles in the body, not inside graphics or icons, since anything rendered as an image is invisible to the parser. Conventional structure is not boring here; it is what lets the system file your information correctly.

Are graphics, icons, and tables a problem?

They can be. Information conveyed only through graphics — a skills bar chart, an icon next to a contact detail, a logo containing text — is invisible to a parser, so anything important must also exist as real text. Tables used for visual layout can confuse parsers into misreading which value belongs to which field, so prefer simple bulleted lists over tables for content. A little visual styling (lines, modest color, bold) is fine; the rule is that no essential information should live only in a graphic or depend on a table being parsed correctly. Put the substance in plain text and use design lightly on top.

How do I check my resume is machine-readable before applying?

Do the copy-paste test: open the PDF, select all, copy, and paste into a plain text editor. What you see is roughly what the ATS sees. If the result is complete, in sensible order, with your name, contact, titles, dates, and bullets all present as text, you are in good shape. If it is scrambled, missing chunks, or empty, fix the formatting (usually: switch to single column, ensure real text, simplify tables). This two-minute test catches the great majority of ATS parsing problems before you submit, and it is far more reliable than guessing whether your design "looks ATS-friendly."

Is it safe to prepare my resume with an online tool?

A resume contains your personal contact details and history, so prefer a tool that processes the file locally. ScoutMyTool checks font embedding, converts between PDF and Word, and optimises files entirely in your browser tab, so your resume never leaves your machine. Many online resume tools upload your file. For a document with your personal data, confirm the tool does not upload before using it.

6 min read

How to format a PDF resume that passes ATS screening

By ScoutMyTool Editorial Team · Last updated: 2026-05-22

A friend could not understand why a beautifully-designed resume was getting no responses — until we ran it through the simplest test and found that her elegant two-column, icon-laden PDF parsed into a scrambled mess, with her job titles interleaved with her skills. The applicant tracking system was not rejecting her format; it was misreading her formatting. That distinction is the whole game. This guide explains how to make a PDF resume that ATS software can actually read: why some PDFs parse badly, the layout and formatting rules that work, embedding fonts, the graphics-and-columns traps to avoid, and the two-minute test that tells you whether your resume is machine-readable before you apply.

Do this, not that

Do this	Not this	Why
Real selectable text	Resume as an image/scan	ATS reads text, not pictures
Single column	Multi-column layouts	Columns scramble reading order
Standard fonts, embedded	Exotic decorative fonts	Parsing + rendering reliability
Standard section headings	Creative section names	ATS maps "Experience", "Education"
Text dates & titles	Info inside graphics/icons	Graphics are invisible to parsers
Simple bullet lists	Tables for layout	Tables can misparse

Step by step — an ATS-readable resume PDF

Ensure the resume is real text. Not an image or scan. If you built it in a graphics tool, recreate it as a text document — see PDF to Word if you need to recover text from an image-based PDF.
Use a single-column layout. Top-to-bottom reading order parses cleanly; keep any two-column designed version only for human readers.
Use standard headings and fonts. "Experience", "Education", "Skills"; standard readable fonts, embedded — verify with Font Embedding Check (see embedding fonts).
Put substance in text, not graphics. Dates, titles, contact, and skills as real text; avoid skills-as-charts and info-bearing icons.
Prefer bullet lists over layout tables. Simple bullets parse reliably; tables used for positioning can misread.
Run the copy-paste test. Select-all, copy, paste into a plain text editor — if it comes out complete and in order, the ATS will read it. Fix anything scrambled.
Follow the posting’s format. If it demands .docx, submit that (convert with PDF to Word); otherwise a clean text-based PDF is fine and keeps your formatting.

PDF to Word: when a posting wants .docx.
Embedding fonts: reliable rendering and parsing.
PDF accessibility: real text and structure (overlaps with ATS-readability).
PDF compatibility: making a PDF open and parse everywhere.
Best PDF tools: tools to prepare the file.
Font Embedding Check: verify fonts before applying.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

Do applicant tracking systems really reject PDFs?: Most modern ATS accept PDFs fine — the myth that "PDFs get auto-rejected" is largely outdated. The real risk is not the format but the formatting: an ATS parses your resume into structured text (name, contact, work history, skills), and if your PDF is hard to parse, fields come through garbled or empty, which can hurt how you rank or match. So the goal is not to avoid PDF; it is to make a PDF the parser can read cleanly. A well-structured PDF resume parses as well as a Word document. When a posting explicitly demands .docx, follow it, but otherwise a clean PDF is fine and preserves your formatting.
What is the single most important rule?: Use real, selectable text — never submit a resume that is an image. If you designed your resume in a graphics tool and exported it as a picture, or scanned a printout, the ATS sees a blank page because there is no text to parse, and you effectively submit nothing. Open your PDF and try to select the text with your cursor; if you cannot, it is an image and will fail. Everything else (columns, fonts, headings) is secondary to this: the resume must contain actual text. If yours is an image, recreate it as a text document and export a text-based PDF.
Why do multi-column resumes cause problems?: Because a parser reads the text in the order it is stored, and a two-column layout can be stored in a way that interleaves the columns — so your left-column skills get mixed into your right-column job descriptions, producing scrambled, low-quality parsed data. A single-column layout reads top-to-bottom in the natural order and parses cleanly. Designers love columns, but for ATS reliability a single column is far safer. If you want a two-column look for human readers, keep a single-column ATS-friendly version for online applications and use the designed version only when handing a resume to a person.
How should I handle fonts and headings?: Use standard, readable fonts and embed them so the PDF renders consistently — exotic decorative fonts can both parse poorly and render as substitutes. For headings, use the conventional section names ATS look for: "Work Experience" or "Experience", "Education", "Skills" — not clever alternatives like "Where I've Made an Impact", which a parser may not recognise as the experience section. Put real text dates and job titles in the body, not inside graphics or icons, since anything rendered as an image is invisible to the parser. Conventional structure is not boring here; it is what lets the system file your information correctly.
Are graphics, icons, and tables a problem?: They can be. Information conveyed only through graphics — a skills bar chart, an icon next to a contact detail, a logo containing text — is invisible to a parser, so anything important must also exist as real text. Tables used for visual layout can confuse parsers into misreading which value belongs to which field, so prefer simple bulleted lists over tables for content. A little visual styling (lines, modest color, bold) is fine; the rule is that no essential information should live only in a graphic or depend on a table being parsed correctly. Put the substance in plain text and use design lightly on top.
How do I check my resume is machine-readable before applying?: Do the copy-paste test: open the PDF, select all, copy, and paste into a plain text editor. What you see is roughly what the ATS sees. If the result is complete, in sensible order, with your name, contact, titles, dates, and bullets all present as text, you are in good shape. If it is scrambled, missing chunks, or empty, fix the formatting (usually: switch to single column, ensure real text, simplify tables). This two-minute test catches the great majority of ATS parsing problems before you submit, and it is far more reliable than guessing whether your design "looks ATS-friendly."
Is it safe to prepare my resume with an online tool?: A resume contains your personal contact details and history, so prefer a tool that processes the file locally. ScoutMyTool checks font embedding, converts between PDF and Word, and optimises files entirely in your browser tab, so your resume never leaves your machine. Many online resume tools upload your file. For a document with your personal data, confirm the tool does not upload before using it.

Citations

Wikipedia — “Applicant tracking system,” how ATS parse and screen applications. en.wikipedia.org — Applicant tracking system
Wikipedia — “Résumé,” on resume structure and conventions. en.wikipedia.org — Résumé
Wikipedia — “PDF” (ISO 32000), why selectable text vs. image determines parseability. en.wikipedia.org/wiki/PDF

Make sure the robot can read you

Check font embedding and convert formats with ScoutMyTool’s in-browser tools, then run the copy-paste test — your resume and personal details never leave your machine.

Open Font Embedding Check →