11 min read
You spent an hour on margins, picked a clean template, and exported a PDF that looked sharp on your screen. Then Workday or Greenhouse chewed it up. Bullets turned into squares. Your phone number landed inside a job description. You're not crazy. The portal didn't show you your file. It showed you what the parser extracted.
That's the core of why resume formatting changes after upload: applicant tracking systems don't preserve design. They pull text into fields so recruiters can search and rank. Before you send another application, check your resume for free against the posting so you're not guessing whether the import worked.
I've screened thousands of imports in Greenhouse and Workday. The candidates who panic usually have strong experience trapped in a layout the bot couldn't read. This guide walks through what breaks, how PDF versus DOCX behaves, and the fixes you can run tonight without buying a new template pack.
You'll get before-and-after examples, a copy-paste rebuild checklist, edge cases for career changers and long employment histories, and portal-specific habits that stop the preview from lying to you.
Quick Wins
- Paste your resume into plain text. If Experience reads out of order, rebuild as a single column today.
- Replace fancy bullets with hyphen lists and re-export as DOCX from Word, not Canva.
- Open the portal preview after upload and fix every scrambled date row before you hit submit.
What happens when resume formatting changes after upload
When you attach a file, the portal runs a parser. That program reads your PDF or DOCX, strips most visual styling, and maps text into structured fields: name, email, work history, education, skills. Recruiters search those fields. They don't scroll your original layout inside the database.
Workday, Greenhouse, Lever, Taleo, and iCIMS each use different parsers, but the goal is the same. Extract searchable text fast. Columns collapse into one stream. Custom fonts revert to defaults. Graphics disappear. Hyperlinks often become raw URLs sitting mid-sentence.
Parser rule of thumb: If a human designer chose it for looks, assume the bot will ignore it or break it. Plain text in a straight line is what survives.
This is not the same as "the ATS hates pretty resumes." The system isn't judging your taste. It literally cannot see two-column alignment the way your eyes do. A qualified analyst with a sidebar template can look unqualified in the preview because job titles attached to the wrong dates.
What this is not: a reason to keyword-stuff or hide white text. Those tricks fail human review and can get you blocked. What it is: a formatting problem you fix once, then reuse on every application. Read resume formatting errors that break ATS parsing for the full list of layout traps.
Step-by-step: fix resume formatting after upload
Step 1: Run a paste test before you blame the portal
Open your file, select all, copy, paste into Notepad or TextEdit. That's roughly what parsers see without your fonts and colors. If the order is wrong here, it will be wrong in Workday.
Before: Two-column Canva export with skills sidebar and icons for each tool.
After: Single-column Word doc, contact line on row one, Skills as a comma-separated line, Experience as stacked blocks with Month Year dates.
Save the paste output in a scratch file named paste-test.txt. Compare it after every template change so you know which edit fixed the scramble.
Step 2: Choose PDF or DOCX with a live test, not a blog rule
You'll hear "always PDF" or "always Word." Both are wrong without testing. PDF exported from Microsoft Word usually keeps visual layout for recruiters who download the attachment. DOCX often gives parsers cleaner access to headings and tables when the portal asks for Word.
Greenhouse frequently accepts both. Workday sometimes parses DOCX employment blocks more accurately when dates sit in simple paragraphs, not table cells. Upload a dummy application to yourself if the company allows, or use a friend's test req.
Before: Scanned PDF from a phone photo of a printed resume.
After: Native DOCX from Word with selectable text, then optional PDF export for attach-only fields.
Never upload a PDF built in design tools unless you've paste-tested it. Canva and InDesign exports look beautiful and import like shredded paper.
Step 3: Rebuild bullets, headings, and contact info
Standard section headings parsers recognize: Experience, Education, Skills, Summary (optional). Creative labels like "Where I've Made Impact" map to nowhere and dump text into a generic bucket.
Put email, phone, city, and LinkedIn URL in the document body. Headers and footers often vanish on import, which is why recruiters see applications with no phone number even though you typed it in the margin.
Operations coordinator example:
Before: Arrow bullets and teal skill bars under a logo header.
After: Hyphen bullets, Calibri 11 pt, "Skills: Excel, SQL, Smartsheet, stakeholder reporting" on one line above Experience.
Registered nurse example:
Before: Table with license info in a left column and jobs in the right.
After: "RN, State of Texas · BLS certified" under name, then reverse-chronological roles with Epic and patient ratio metrics in plain bullets.
Step 4: Fix dates, tables, and overlapping roles
Tables are resume perfume. They smell professional in Word and explode in parsers. Replace them with tab-separated lines or simple stacked entries. Use Mon YYYY consistently: Mar 2021 to Present, not 03/21 or 2021-03.
Contract overlaps need one line of context: "Concurrent contract while employed full-time at Acme" beats two date rows fighting for the same months without explanation.
After upload, open the portal's review screen. Workday lets you edit parsed rows. Do it on a laptop, not your phone, when history is longer than three jobs.
Step 5: Preview, edit parsed fields, then submit
Many candidates upload and immediately click submit. The preview step exists so you can fix parser mistakes before recruiters inherit them.
Scroll every employment block. Confirm employer name, title, start month, and end month. If a bullet merged into a job title field, shorten the title line in your source file and re-upload.
Greenhouse sometimes shows a parsed resume tab beside the original PDF. Read the parsed view, not just the thumbnail. That's the version keyword matching often uses.
Edge case: career changers with design-heavy old resumes
Graphic designers and marketers often have portfolio layouts that should never go through a corporate parser. Keep a boring single-column "application version" for portals and link a portfolio site in the contact line when the posting allows URLs.
Translate creative titles into plain language the req uses. "Visual storyteller" becomes "Marketing Designer" if that's what the posting says. Parsers and recruiters both match literal title strings.
Edge case: ten-plus years and multiple pages
Long files amplify parsing errors. Compress roles older than ten years to two lines each. Keep page one for the last three jobs that match this posting. Parsers that choke on page three still cost you if page one scrambled.
If the portal caps upload size, export PDF at standard quality, not print shop 600 dpi. Huge files sometimes fail silently and fall back to partial text extraction.
Copy-paste rebuild checklist (15 minutes)
Open Word. Set margins to 0.7 inch. Font Calibri or Arial 11 pt. Paste plain text from your paste test. Re-type section headers in Title Case on their own lines. Rebuild jobs as:
Job Title · Company Name · City, ST
Mon YYYY to Mon YYYY or Present
- Action verb + tool + outcome with number or scale
- Second bullet with posting keyword in the first eight words
Repeat for each role. Save as DOCX. Export PDF from Word only. Paste-test again. Stop when Experience reads cleanly top to bottom.
That block is boring on purpose. Boring is what Greenhouse and Workday import without surprise. For file-type nuance, see how resume file type impacts screening .
Second composite: account executive with broken columns
Before: Two-column resume with quota stats in a shaded right rail.
After: Single column, first bullet under current role: "Exceeded annual quota at 118% across 42 enterprise accounts in Salesforce CRM, avg deal size $280K."
Same achievements. Different container. The parser can finally attach numbers to the right employer.
Common mistakes when resume formatting breaks after upload
Trusting the PDF thumbnail. The attachment preview often shows your original layout. The parsed record can still be wrong. Always open the text import view.
Using text boxes for alignment. Text boxes look like clean spacing in Word. Parsers skip them or dump content at the bottom of the file out of order.
Submitting the same broken file to ten portals. If paste-test fails once, it fails everywhere. Rebuild before you burn openings you wanted.
Choosing PDF when the posting requires DOCX. Some Workday configs reject or mangle non-compliant uploads. Read the fine print on the attach button.
Hiding contact info in a header. Recruiters can't call you if the parser dropped your phone line. Put it under your name in the body every time.
Ignoring the application form after upload. Parsed resume plus manual form must match. Different dates on the form and file trigger recruiter doubt and sometimes auto-reject rules.
Adding graphics to "stand out." Skill bars, charts, and headshots strip out. They don't make you memorable. They make your keywords disappear.
Test upload formatting before the real application
Run your rebuilt DOCX or PDF through HireFlow's free ATS resume checker with the job description pasted in. It flags sections parsers miss, date gaps, and keyword alignment problems. You see parser-style output without wasting a live submission.
Compare two exports side by side: Word PDF versus native DOCX. Send the version that parses with more complete Experience rows, even if the PDF looked prettier in Preview mode.
When the role asks for a cover letter, draft with the cover letter generator , then verify employer names match the resume version you're uploading. Mismatched names are a silent filter after formatting is fixed.
Pair this check with the most common ATS resume formatting mistakes so you're not re-fixing the same layout error on every Friday night application batch.
Stop fighting the preview. Fix the file once.
Why resume formatting changes after upload comes down to one fact: portals read text, not design. Workday and Greenhouse strip your layout so recruiters can search and rank. Build a single-column DOCX or Word-exported PDF, paste-test it, fix parsed rows in the preview, then submit.
- Paste-test before every new template. Scrambled order in Notepad means scrambled order in the ATS.
- Test PDF and DOCX when allowed. Keep the format that imports dates and titles correctly.
- Edit parsed fields on the portal before submit. Don't assume the attachment view is what recruiters search.
Open your file, run the free resume check , rebuild the first section the report flags, and save a new version. That's how you stop losing interviews to a parser that never saw your best bullet.
Read more
Frequently asked questions
The portal converts your file to searchable text. Layout, colors, and columns don't transfer. What you see is often a parser preview, not a corrupted copy of your design. Fix the source file, not the preview skin.
Follow posting rules first. When both are accepted, paste-test each format and pick the one that keeps dates and titles on the correct rows. Many teams keep DOCX for parsing and PDF only when required.
Replace custom bullets with hyphens or standard round dots in Word before export. Fancy icons map to garbage characters in plain-text conversion. Re-upload after you rebuild the list.
Parsers flatten columns into a single stream read left to right. Sidebars inject contact info between job bullets. Move everything to one column with contact details at the top of the body.
No. Format work stops qualified candidates from getting filtered by accident. It won't create skills you don't have. Fix readability first, then decide if the role is a fit worth tailoring toward.
