Is PDF or DOCX better for an ATS?

Both carry a text layer when exported from an editor, so either is fine. Send the form you would actually submit. A PDF preserves your layout across machines, which makes it the safer choice for design you care about; a DOCX reflows when a word processor opens it, so the page you sent may not be the page they saw.

Can I use a two-column resume if it is ATS friendly?

Not for body content. A second column is the single most common way to lose text, because extraction walks across the page rather than down each column. A one-column file with a strong heading structure is the format that survives. If a layout template insists on two columns, move everything into one before you send it.

Do graphics, icons, and progress bars hurt my resume?

They usually do, and rarely for the reason people think. An icon or a bar chart carries no characters, so a skill rated with dots extracts as nothing. Replace the graphic with the word or the number the graphic was meant to show, and the information arrives.

How do I know my format is ATS friendly before I apply?

Run the file through a checker that shows you the extracted text, not just a verdict. Look for three things: your contact details present, your sections in the order you wrote them, and nothing missing between the first line and the last. Then fix what the file breaks, not what the design guide says.

ATS friendly resume format

An ATS friendly resume format is one a parser can turn into text in the order you wrote it. Not a plain look, not a special font: a file whose text layer, column order, and headings survive extraction. This page explains what a parser actually reads, the eight layout habits that break it, and how to check your own file before you send it.

What an applicant tracking system actually receives

You see a designed page. The system sees a text file it has to rebuild. When a resume arrives, an applicant tracking system runs an extraction step first: it pulls the characters off the page, drops them into fixed fields like name, employer, title, dates, and skills, and only then shows a recruiter something readable. Every judgement about your format is made in that first step, before a person has seen your work.

That is why an ATS friendly resume format is not about looks. A two-column layout can look sharp and still come back with a phone number stranded in the middle of a sentence. A single-column file with a text box behind it can lose an entire section in silence — the recruiter sees a short resume, not a broken one. Nothing warns you. The extraction simply returns less than you wrote.

Text extraction reads the page in the order the text objects were drawn, and it reads left to right across the page. So position matters more than style. A file built in one column, top to bottom, with normal headings and no containers, gives the parser the same order you read. Anything else asks that parser to guess, and a guess costs you a field.

There is a second, smaller trap before format even starts: the file must carry a text layer at all. A scanned PDF is a picture of a resume. It has no characters to pull, so extraction returns an empty string. Export a text-based PDF from Word or Google Docs, upload the DOCX itself, or paste the text. If you are not sure which one you have, open the file and try to select a single word with the mouse. If you cannot select it, no parser can either.

Eight format habits that break extraction

A file with no text layer

What you see: The resume comes back empty, or the system reports that it could not parse the document and asks you to re-enter your history by hand.
Why it happens: A scan or an image-only PDF holds pixels, not characters. Extraction has nothing to read, so it returns nothing to the fields.
How to fix it: Export from the editor instead of printing to PDF. In Word, use Save as PDF. In Google Docs, use Download as PDF. Keep the DOCX as your source file and send the PDF it produces.

Two columns of body content

What you see: Skills from the right column appear in the middle of a sentence from the left one, and a whole work history arrives out of order.
Why it happens: The parser walks the page left to right across, not down each column. Two columns become one interleaved stream unless the software stitches them back, and most do not.
How to fix it: Put every piece of real content in one column. If you want a sidebar look, keep it to nothing a recruiter would miss — a column of dates alone still breaks the order.

Tables and text boxes holding content

What you see: A section vanishes. The parsed output jumps from your summary straight to education, and the skills block in between is simply absent.
Why it happens: Parsers treat containers as decoration or read them out of sequence. Text inside a table cell or a floating box is the most common content lost in full.
How to fix it: Use headings and plain paragraphs. Replace a skills table with a heading and comma-separated lines. If the layout is held together by tables, rebuild it without them.

Contact details in the page header or footer

What you see: The parsed profile has no email and no phone number, and the system asks you to type them into a form.
Why it happens: Header and footer regions are often skipped by extraction because they repeat on every page. People put contact details there precisely because they repeat.
How to fix it: Write your name, email, phone, city, and links as body text on the first page, above your summary. Then check that the fields are really in the text stream.

Creative section headings

What you see: Work history lands in a notes field. Education is not recognised, so degree and institution go unparsed.
Why it happens: The parser maps fields by heading words it knows. A clever heading reads fine to a person and matches no field in the system.
How to fix it: Use the ordinary names: Work Experience, Education, Skills, Summary. Save the personality for the bullets, where a person reads it and no field mapping depends on it.

Mixed date styles

What you see: A ten-year career is read as three years, or an end date is missing and the role appears open.
Why it happens: Extraction parses dates with patterns. When one role uses 03/2019 and another uses March 19, only one of those patterns is matched, and the field stays blank.
How to fix it: Pick one style and use it everywhere, for example MM/YYYY. Put the same style on every role, on education, and on any dated certification.

Type size and margins outside the readable range

What you see: Small print under a crowded margin extracts as fragments, and single characters break onto their own lines.
Why it happens: Extraction groups glyphs by position and size. Very small type and very wide margins push lines so close together that separate rows merge.
How to fix it: Stay in the range a word processor gives you by default: an ordinary body size, margins that are not narrowed to squeeze a page, and no letter-spacing tricks.

A page count that does not fit the career

What you see: A senior role arrives as a single crowded page, or a first job runs to six pages of prose.
Why it happens: Recruiters read the length as a signal, and systems flag outliers. A trimmed senior history looks thin; an unedited early career looks unfinished.
How to fix it: Match length to experience. One page is honest for a student or a career changer. Two pages carry most professionals. Cut the oldest, least relevant roles before you cut achievements.

What is an ATS compliant resume?

An ATS compliant resume is a file that extraction can read completely and in order. Compliance is not a certificate and there is no standard body that issues one. It is a set of properties you can check: the file carries a text layer, the content sits in one column, containers hold nothing important, contact details live in the body, headings use ordinary words, dates share one style, and length fits the career.

Two claims you will see elsewhere are worth ignoring. First, there is no secret keyword density that makes a resume compliant; systems extract your words, they do not grade how many you packed in. Second, no applicant tracking system publishes its weights to candidates, so any page that quotes an exact number from a named vendor is guessing. What you can control is whether the fields arrive intact, and that is a format question.

Compliance also does not mean plainness. A one-column file with clean headings, ordinary type, and consistent dates can still read well to a person. The format decisions that cost you are the ones that move text out of the stream or reorder it — not the ones that make the page look designed.

A compliant format checklist

A compliant format checklist
Do	Do not
Send a text-based PDF exported from the editor, or the DOCX itself.	Do not send a scan, a photo, or a resume flattened into an image.
Run body content in one column, top to bottom, in the order you want it read.	Do not split skills, roles, or education into a second column for balance.
Use headings a parser knows: Work Experience, Education, Skills, Summary.	Do not rename sections to something clever that maps to no field.
Put name, email, phone, city, and links as body text on page one.	Do not leave contact details only in the repeating header or footer.
Pick one date style, such as MM/YYYY, and repeat it on every entry.	Do not mix March 2019 with 03/2019 across sections.
Keep default type size and margins, and let the page run to two if needed.	Do not shrink text or narrow margins to force a one-page limit.
List skills as plain lines or comma-separated items under a Skills heading.	Do not bury a tool list inside a table, a box, or three sentences of prose.
Re-open the finished file and select a word with the mouse to confirm the text layer.	Do not trust the file name or the extension as proof anything is readable.

How an ATS resume format check works

A format check tests the properties above against your actual file, then reports which ones hold. Ours runs seven format checks and five content checks in your browser, and weights them 40 and 60 points. Format answers one question: can a parser rebuild your page as text in the right order. Content answers a different one: does the text it got back contain what a screen looks for. A high total with a weak format half means your writing is fine and your file is the problem.

Some checks go quiet depending on how you submit. Pasted text carries no coordinates, so column, margin, and page-count checks cannot run. A DOCX reports no glyph sizes, so the type-size check does not either. Those items are removed from the denominator rather than counted against you, which is why the same resume can score differently as a PDF, as a DOCX, and as pasted text. Test the form you intend to send.

The score is computed by code with fixed weights, so the same file returns the same number every time. No model is involved, and nothing is uploaded: the file is parsed in the tab you are reading, and no request carries your resume. If you want the exact text a parser would rebuild from your page, the free ATS resume checker shows that line by line next to the order you actually read, so the damage from a second column is something you can see rather than guess at.

See what your own file gives up

Format problems are invisible on the page you designed. The only honest test is the extracted stream: drop your resume into the free ATS resume checker and read the text a parser rebuilds from it, line by line, next to the order you actually read. It runs in your browser, needs no account, and nothing is uploaded.

free ATS resume checker

Questions about resume format for ATS

Is PDF or DOCX better for an ATS?: Both carry a text layer when exported from an editor, so either is fine. Send the form you would actually submit. A PDF preserves your layout across machines, which makes it the safer choice for design you care about; a DOCX reflows when a word processor opens it, so the page you sent may not be the page they saw.
Can I use a two-column resume if it is ATS friendly?: Not for body content. A second column is the single most common way to lose text, because extraction walks across the page rather than down each column. A one-column file with a strong heading structure is the format that survives. If a layout template insists on two columns, move everything into one before you send it.
Do graphics, icons, and progress bars hurt my resume?: They usually do, and rarely for the reason people think. An icon or a bar chart carries no characters, so a skill rated with dots extracts as nothing. Replace the graphic with the word or the number the graphic was meant to show, and the information arrives.
How do I know my format is ATS friendly before I apply?: Run the file through a checker that shows you the extracted text, not just a verdict. Look for three things: your contact details present, your sections in the order you wrote them, and nothing missing between the first line and the last. Then fix what the file breaks, not what the design guide says.