Why a resume that looks fine can still break
Most job applications don't just accept your PDF as-is. Somewhere behind the "Upload Resume" button, software often extracts the text from your file — either to store it in a database, auto-fill an application form, or feed it into an applicant tracking system for a recruiter to search later. That extraction step is where formatting problems that were invisible on your screen suddenly become visible as garbled text, missing sections, or fields filled in wrong.
This guide walks through the specific formatting choices that cause that, in the order you're likely to encounter them while building a resume, with a real fix for each.
Step 1: Build in a single column, not a two-column layout
Two-column resumes — usually a narrow sidebar for skills/contact info next to a wider main column for experience — look sharp in a template preview but are the single most common cause of scrambled parsing. Text-extraction tools generally read left to right, top to bottom, in a straight line. A two-column layout means the software often reads one line from the left column, then one from the right, interleaving your contact info, skills, and experience into nonsense order.
Fix: use a single-column layout, especially for your core content (experience, education, skills). If you want visual structure, use clear section headings and spacing rather than side-by-side columns.
Step 2: Keep contact information out of the header/footer
Word processors let you place your name and contact details in a document header, which looks clean and stays fixed at the top of every page. The problem: many parsing tools skip headers and footers entirely, treating them as page furniture rather than content — which means your name, email, and phone number can vanish from the extracted text even though they're clearly visible when you look at the file.
Fix: put your name and contact details in the main body of the document, as the very first block of text, not in a header/footer field.
Step 3: Avoid tables for layout
Tables are tempting for aligning dates against job titles, but like columns, tables can extract in an unpredictable reading order — a date in one cell and a job title in the adjacent cell might not come out next to each other in the parsed text.
Fix: use tab stops or simple left/right alignment within a normal paragraph line instead of an actual table structure, or accept a slightly less rigid alignment in exchange for text that extracts cleanly.
Step 4: Don't put section headings, skills, or your name inside an image
Some templates render the header — your name, a decorative line, sometimes even your job title — as a graphic or an icon-based skills bar rather than as real text. Anything rendered as an image is invisible to a text-extraction tool; it simply doesn't exist in the parsed output, no matter how good it looks visually.
Fix: every piece of information you need read — your name, your section headings, your skills — should be actual typed text, not an image, icon set, or embedded graphic. Small logo-style icons next to a phone number or email are usually fine since the text itself is still real text next to them; the risk is specifically when information itself is baked into an image.
Step 5: Use standard section headings
"Experience," "Education," "Skills," and "Summary" are recognized reliably. Creative renamings — "My Journey," "Where I've Been," "The Toolbox" — read as clever to a human but can confuse a system trying to identify which block of text is which category of information, and even a human reviewer skimming quickly benefits from headings they don't have to decode.
Fix: stick to conventional headings. Save the creativity for your bullet content, not your section labels.
Step 6: Clean up hidden formatting from copy-paste
If you wrote your resume by pasting content between Word, Google Docs, and a browser-based form at different points, it's common for invisible leftover formatting — stray font changes, odd spacing characters, leftover styles from a template — to accumulate in ways you can't see just by looking at the page. This is especially common with bullet points copy-pasted from one document into another, which can carry hidden list-style metadata that renders oddly once it hits a different system.
Fix: if your resume has passed through multiple documents or tools, run the final text through Craftume's Resume Formatter before your final export — it's built specifically to strip out this kind of inconsistent, invisible formatting cruft and leave clean, consistent text behind.
Step 7: Save as a proper PDF, and check the file itself
Once your resume is finished, export it as a PDF (the format most employers expect, and the one least likely to shift its layout on someone else's screen). Two things are worth checking on the file you're about to send:
- File size — an unnecessarily large PDF (sometimes from an embedded high-resolution photo or leftover design assets) can be slow to upload or occasionally get rejected by an application form with a size limit. Craftume's PDF Optimizer shrinks file size without visibly degrading quality, which is worth doing if your file feels larger than a plain text-and-layout document should be.
- Embedded metadata — PDFs carry hidden document properties (author name, the software that created it, sometimes a creation date) that you may not have noticed if you started from a template someone else built. Craftume's Metadata Viewer shows you exactly what's embedded in your file, which is a quick way to confirm it says what you'd want it to say if anyone ever looked (and occasionally people do).
Step 8: Do one final read-through in plain text
Before you send your resume anywhere, copy the text out of your finished PDF and paste it into a plain text editor (like Notepad). This shows you approximately what a parsing tool sees: no formatting, no layout, just the raw text in the order it was extracted. If names, dates, or bullet points come out jumbled, misordered, or missing in this view, that's a preview of the same problem happening on the other end when an employer's system does it automatically.
A quick pre-send checklist
- Single column, no side-by-side layout for core content
- Contact info in the body, not a header/footer field
- No tables used for alignment
- No text embedded inside images or icon graphics
- Standard section headings
- Formatting cleaned of copy-paste artifacts
- File size reasonable, checked with the PDF Optimizer
- Metadata checked and clean
- Plain-text copy-paste test passed
- Final pass through the Resume Checker for anything else structural
FAQ
Is a .docx file safer than a PDF for avoiding formatting issues? Not necessarily — .docx files can actually render differently depending on which version of Word (or which non-Word program) opens them, where a PDF renders identically everywhere. Unless an application specifically requests .docx, PDF is generally the safer default for visual consistency, provided you've followed the steps above for the text underneath it to extract cleanly too.
Do icons next to my phone number and email cause parsing problems? Small decorative icons are usually fine as long as the actual phone number and email are typed text next to them, not part of the icon graphic itself. The risk is specifically when information you need read is baked into an image rather than typed.
How do I know if my current resume has a two-column layout problem? If your skills, contact info, or a summary sits in a narrower side panel next to your main experience column, that's a two-column layout. A quick way to check: try selecting all the text in the document and copying it — if the pasted result interleaves unrelated sections, that's the same issue a parser would hit.
Is it ever okay to use a two-column layout? If you know for certain a specific application process is reviewed by a human directly (no upload-and-parse step, no tracking system) a two-column design can look sharp. Without that certainty, a single-column layout is the safer default since you can't usually tell which review process a given employer uses.
Should I keep a plain, no-design version of my resume as a backup? It's a reasonable habit — having one clean single-column version ready means you're never stuck reformatting under time pressure if an application specifically warns about parsing issues or gives you a plain-text paste box instead of a file upload.