NewApply for you — a dedicated human applies to 1,000+ jobs on your behalf
11 min read

How to Check If Your Resume Is ATS-Friendly: Four Free Tests, in the Order That Finds the Problem

You cannot tell if a resume is ATS-friendly by looking at it. Run the paste test, the search test, a real application form's parsed preview, and a keyword check, in that order, before you trust any scanner score.

You check whether a resume is ATS-friendly by testing what software can pull out of the file, not by looking at the page. Four tests do that for free in about fifteen minutes: paste the text into a plain editor, search the file for your own details, upload it to a real application form that shows you the parsed fields, and compare what parsed against the posting. Run them in that order, because each one isolates a different cause of failure. A scanner score can come after, and it will tell you less than the third test does.

Most guides stop at the paste test, or skip straight to a checker tool and treat its score as the answer. The score is a model of a parser, not the parser. The employer's own application form shows you the real thing, and nobody charges for it.

What does "ATS-friendly" actually mean?

Two separate properties get bundled under the phrase, and they fail for different reasons.

The first is parseability: can the applicant tracking system extract your name, contact details, employers, titles, dates, education and skills from the file and put each in the right field? This is a formatting and file question. Columns, text boxes, header-only contact details and image-based PDFs break it.

The second is searchability: once the text is in the system, does a recruiter's search for a term find it? This is a content and encoding question. A skill you never wrote down will not be found, and neither will one written with a character the search does not match. For the background on what the system does with your file, see what ATS means on a resume. The four tests below check both properties, two each.

Test 1: What does the paste test show?

Open the file you would actually upload, select all, copy, and paste into an editor that strips formatting: Notepad on Windows, TextEdit in plain-text mode on a Mac, or any code editor. Use the exported PDF or DOCX, not the design file it came from, because the export is what the parser gets.

Read the result from the top and check five things:

  • Your name is on the first line, with your email and phone within the first few lines.
  • Sections appear in the order you intended, with nothing from a sidebar wedged into the middle of your experience.
  • Each job reads as a block: employer, title, dates, then bullets.
  • Bullets survived as characters, not as blank lines or stray symbols.
  • Nothing is missing. A section you can see on the page but not in the paste was probably an image or a text box.

Interleaved text is the classic two-column failure. The parser reads across the page, so a skills sidebar ends up chopped into your work history line by line. A paste that comes back empty means the PDF has no text layer, which happens when a design tool exports the text as shapes or when the file is a scan.

Pass this test and you know the text exists and the reading order is sane. You do not yet know whether the system can find anything in it.

Test 2: What does the search test catch that the paste test misses?

Now use the find function inside the PDF or Word file itself. Search for your phone number, your email, one skill the posting treats as mandatory, and one hyphenated term from your resume such as "cross-functional".

Each search should return a hit. When visible text returns zero hits, the characters on the page are not the characters you think they are. The common causes:

  • Ligatures. Some fonts and export settings fuse letter pairs like "fi" and "fl" into a single glyph. The word looks normal and reads normally, but a search for "certified" or "workflow" typed with ordinary letters can miss it.
  • Non-standard hyphens and dashes. AI writing tools and some editors emit a non-breaking hyphen (Unicode U+2011) or an en dash where a plain hyphen belongs. "Cross-functional" with the wrong hyphen will not match a search for "cross-functional" with the keyboard one. This is a quiet defect because the page looks identical.
  • Curly apostrophes. "Bachelor's" with a typographic apostrophe can miss a search typed with a straight one. Same mechanism, lower stakes.
  • Text as outlines. If the paste test came back empty, the search test will too. Fix the export first.

A recruiter searching a candidate database types ordinary characters, so their search behaves the way your find box does. The fix is the same for all of these: retype the suspect term with your keyboard and re-export. If you tailor with any AI tool, run the search test on every export, because this is where the bad characters come from.

Test 3: How do you see what the employer's ATS actually parsed?

This is the test the other guides skip, and it is the only one that uses a real parser. Most large employers run applications through a system that reads your resume and pre-fills the form from it. Workday shows a review screen after upload, with your experience and education already filled in from the file. Greenhouse and Lever job boards offer to autofill the application from your resume.

Pick one live posting you were going to apply to anyway, upload the resume, and stop at the review screen. Read every field the system filled:

  • Employer and title on each job. A missing job usually means its heading was not recognised, often because the employer and title were on the same line in an unusual order, or because the section heading was creative rather than "Experience".
  • Dates. Wrong or empty dates point to an inconsistent date format. Pick one style and use it everywhere.
  • Education. Degree, school and year should land in three separate fields. If they merged, the line that holds them is formatted in a way the parser could not split.

Note what broke, fix the file, and upload again. Workday lets you correct the fields by hand before you submit, so a parse error is recoverable there. Plenty of smaller systems have no review step, and whatever the parser extracted is what gets stored. That asymmetry is why you test on a form that shows you the result, then trust the fixed file everywhere else. Do not submit until the file is fixed, since some systems will not let you replace the first upload.

Test 4: Does the file say what the posting asks for?

Tests one to three establish that the system can read you. Test four asks whether it will find you for this job. Open the posting, pull the terms from the qualifications section that a recruiter would plausibly search for, and check each one against the pasted text from test one. Pull them by hand or with the free job keywords tool.

A missing term is a content gap, which is a different problem from a parse failure. Do not fix it by appending a keyword block. Fix it by rewriting the bullet where you actually did the thing so it uses the posting's word for it. How to tailor your resume for ATS walks through that rewrite. If you are doing this for many postings, LetMeApply's ATS resume optimizer runs the comparison and shows which required terms are absent, and AI resume tailoring proposes bullet edits for you to accept or reject. Run test two on whatever it exports, the same as on your own file.

What breaks each test, and what fixes it

Symptoms map to causes fairly cleanly, which is the point of running the tests in order.

  • Paste is empty or garbage. No text layer. Re-export from the source document with text preserved.
  • Paste interleaves two sections. Multi-column layout. Move to a single column, with skills as a plain list under their own heading.
  • Contact details missing from the paste. They are in the header or footer. Move them into the body under your name.
  • A whole section missing from the paste. It sits in a text box or an image. Convert it to body text.
  • Visible word returns zero search hits. Ligatures, non-standard hyphens or quotes. Retype and re-export.
  • A job is missing from the parsed preview. Heading or line-order problem. Use standard section names and put employer, title and dates on predictable lines.
  • Dates empty or wrong in the preview. Inconsistent date format. Use one format throughout, with a month and a year.
  • Required term absent from the paste. Content gap. Rewrite the relevant bullet, do not stuff a keyword list.

Fonts matter less than most checklists suggest, as long as the text is real text. A standard font is a sensible default because of the ligature issue, not because a parser refuses Garamond.

When should you use a scanner, and what does the score add?

After the four tests, a resume checker is useful for one thing: a quick estimate of term overlap between your resume and one posting. That is a faster test four, and its gap list is worth reading.

It is weak at the things tests one through three catch. A checker cannot tell you how the employer's parser will handle your layout, it rarely shows reading order, and its score is its own invention rather than anything the employer sees. Does your ATS resume score matter explains why two tools give the same file different numbers. Treat the score as a to-do list, and a clean parsed preview on a real form as the actual pass mark.

How often should you re-run the checks?

Run all four when you build a new base resume, and whenever you change the layout or the template. After that you can be selective. Content edits inside an existing layout rarely break parsing, so a tailored copy needs test two on the export and test four against the new posting.

Re-run test three whenever you touch structure: a new section, a reordered section, a different date format, or a switch between PDF and DOCX. Each of those is a parse change rather than a content change, and the only way to know how it lands is to watch a real form read it. Once your base file passes cleanly, the routine for a new application is a couple of minutes.

Frequently asked questions

Is PDF or Word safer for an ATS?

Use whichever the form asks for. If it accepts both, run the paste test on both exports and submit the one that pastes cleanly. Neither is wrong unless the paste test says so.

Can an ATS read a two-column resume?

Sometimes, and you cannot know which times in advance. Newer parsers handle some two-column layouts and older ones interleave them. A single column loses nothing and removes the risk, so it is the safer default for the file you upload.

Does a photo or an icon fail the check?

A photo does not break parsing by itself, but it is dead space to the parser and some employers strip it for compliance reasons. Icons are the quieter problem: a phone icon next to a number may parse as a number with no label. Spell out "Phone" and "Email" in text.

Can I check without uploading my resume to a third-party site?

Yes. Tests one and two use only your own computer, and test three uses the employer's form. Only a scanner involves a third party, and it is the optional step.

My resume passes every test and I still hear nothing. What now?

Then the file is not the problem, and more formatting work will not help. Look at fit, volume and timing: whether the roles are a real match, how many you apply to, and how soon after a posting goes live. The parse checks only confirm the system can read you. They cannot make a weak match strong.

Related articles