10 Resume Formatting Mistakes That Can Confuse Parsers

You can have relevant experience and still lose useful detail when a resume parser misreads the document. Parsing behavior varies, but ambiguous structure can reorder text, hide fields, or split entries in ways worth checking before submission.

Here are the 10 most common formatting mistakes, why they break ATS parsing, and how to fix each one.

1. Using Tables for Layout

Tables are one of the most common resume design tools, and one of the worst for ATS compatibility. Most ATS platforms read content in a linear stream. When they encounter a table, they may read across rows (mixing data from different columns) or skip table content entirely.

The fix: Use a single-column layout with clear section breaks. If you need a compact skills section, list skills inline with commas or pipe characters instead of a table grid.

2. Putting Contact Info in the Header

Word processors and Google Docs have a header area that appears at the top of every page. It seems like the perfect place for your name and contact info. The problem: many ATS platforms ignore document headers and footers entirely. Your name, email, and phone number become invisible.

The fix: Place your contact information in the main document body, at the very top. Use regular text, not a header/footer block.

3. Images, Logos, and Icons

Star ratings for skills. A headshot photo. Company logos next to each job. LinkedIn and email icons. These all look professional to a human reader, but ATS software cannot read text inside images. If your phone number is displayed as an icon followed by digits inside a text box, the ATS may only see the digits without context.

The fix: Remove all images from the resume body. Use plain text labels instead of icons. Write "Email: you@example.com" instead of using a mail icon. Skills should be listed as text, not rated with star graphics.

4. Creative Section Headings

ATS systems look for standard section headings to understand the structure of your resume. They expect to find "Experience," "Education," "Skills," and "Summary." When you use creative headings like "Where I've Made My Mark" or "My Professional Story," the parser may not recognize the section at all.

The fix: Use standard headings. Acceptable variations include "Work Experience," "Professional Experience," "Technical Skills," and "Professional Summary." Avoid anything clever or unique.

5. Inconsistent Date Formats

Dates tell the ATS how long you worked at each job. If your dates are inconsistent (mixing "Jan 2023" with "2022-03" with "March, 2021"), the parser may fail to extract employment duration. Some systems will show gaps in your employment history that do not actually exist.

The fix: Pick one date format and use it everywhere. "Month Year" (e.g., "January 2023" or "Jan 2023") is the safest and most widely recognized format. Always include both start and end dates, or "Present" for your current role.

6. Multi-Column Layouts

Two-column and three-column layouts pack more content into less space, but they create parsing ambiguity. The ATS does not know whether to read left column first then right column, or to read across both columns as a single line. The result: text from your skills column gets merged with text from your experience column, creating nonsensical content.

The fix: Use a single-column layout for maximum ATS compatibility. If you need a sidebar for skills or contact info, keep it simple and test the output with an ATS checker to verify correct parsing.

7. Text Boxes and Shapes

Text boxes in Word or Google Docs are floating elements that sit above the document flow. ATS parsers that read the document stream may skip floating text boxes entirely, or they may read them out of order. A skills section in a text box might end up parsed after your education section, or not parsed at all.

The fix: Use regular paragraphs and headings for all content. Never place text inside a shape, text box, or floating element. If you want visual separation, use horizontal lines or extra spacing.

8. Fancy Fonts and Special Characters

Unusual fonts may not have proper character mapping in PDF exports. Special characters like curly quotes, em dashes, or decorative bullet characters can be converted to garbled text or question marks during parsing. The information is there, but the ATS cannot decode it.

The fix: Stick to standard fonts: Arial, Calibri, Garamond, Georgia, Helvetica, or Times New Roman. Use standard bullet characters (round dots) and plain hyphens instead of decorative characters.

9. Missing or Incorrect File Format

Not all file formats parse equally. Some key differences:

• .docx is widely accepted, but compatibility still depends on the employer's portal and parser. Follow the file types listed in the job posting.
• .pdf works well if the text layer is intact. PDFs exported from Word or Google Docs are usually fine. PDFs exported from Canva, Figma, or design tools may have text stored as paths rather than characters, making them unreadable.
• .doc (legacy Word) is becoming less supported. Avoid it.
• .pages, .odt, .rtf may not be accepted at all by some portals.

The fix: Submit .docx unless the application specifically requests PDF. If you submit a PDF, open it in a PDF reader and try to select and copy text. If you cannot select the text, the ATS cannot read it either.

10. Overly Dense or Compressed Content

Shrinking margins to 0.3 inches, reducing font size to 9pt, and eliminating all whitespace might let you fit more content on one page, but it creates parsing problems. Extremely tight spacing can cause the ATS to merge separate sections. Tiny fonts may trigger heuristic filters that flag the resume as difficult to read.

The fix: Use 10-12pt font for body text, 0.5-1 inch margins, and clear spacing between sections. If your resume does not fit on one page at readable sizes, cut content rather than compressing formatting. Two clean pages are better than one cramped page.

How to Test Your Formatting

A practical way to inspect formatting risk is to run your resume through a parser and review its output. Check that:

• Your name and contact info are extracted correctly
• Each job appears as a separate entry with the right title, company, and dates
• Skills are identified as a distinct section
• No text is missing or garbled
• Sections are in the right order

PrismCV's free ATS checker shows what its own parser extracts and applies the documented v3 diagnostic to parse readiness, content strength, and job relevance. It requires no signup. Review the methodology and limitations; the result is not a simulation of every employer's ATS.