Back to Blog

How to Convert Your Resume to ATS Format (Free, in 10 Minutes)

Convert any fancy resume into an ATS-friendly format in 10 minutes: strip tables and columns, fix headers, choose docx or PDF — step by step.

How to Convert Your Resume to ATS Format in 10 Minutes

Converting a resume to ATS format means rebuilding it as a single-column document with standard section headings, body-text contact details, and no tables, columns or text boxes — then saving it as .docx (or a clean text-based PDF) so applicant tracking systems parse every field correctly. The job takes about ten minutes once you know the seven fixes below, and it routinely rescues applications that were silently failing because parsers couldn't read the design. This is the practical companion to our complete ATS mastery hub, which covers how parsing and ranking work under the hood.

First, understand what you're fixing: an ATS doesn't "see" your resume — it extracts text in reading order and maps it into fields (name, contact, skills, employment history). Design elements that look great to humans scramble that extraction. Every step below removes one scrambling risk, in the order most conversions need them.

Before You Start: The 30-Second Diagnostic

Not sure whether your resume even needs conversion? Run this quick check:

  1. The paste test: open your file, select-all, copy, and paste into Notepad or a plain-text editor. Missing phone number? Jumbled columns? Invisible skill bars? Those exact losses happen inside parsers.
  2. The zoom-out test: shrink the page to thumbnail size. If your layout depends on side-by-side columns to make sense, it will not survive extraction into linear text.
  3. The heading test: can you spot "Experience", "Education" and "Skills" as plain words? If they're images, icons or stylised graphics, mapping fails.

Fail any one and the ten-minute conversion below is worth your evening. Pass all three and you may only need the docx-vs-PDF decision at step six — but verify anyway; most designed resumes fail at least one test.

Step 1: Move Contact Details Out of Headers and Footers (2 minutes)

Open your file in Word. If your name, phone number or email live in the header/footer area, cut them and paste into the main document body at the top.

  • Why: many parsers skip headers and footers entirely, producing CVs with no phone number attached — recruiters searching results never see you.
  • Format: Name on line one; phone | email | city | LinkedIn on line two. No icons, no graphics.

Header contact loss is one of the most common of the ATS mistakes that auto-reject good candidates — fix it first because everything else depends on being identifiable.

Step 2: Strip Tables, Columns and Text Boxes (3 minutes)

Select any table and use Word's Table Layout → Convert to Text (separated by tabs), or simply copy content out and retype it as plain lines. Delete all two-column layouts by moving right-column content beneath left-column content. Remove text boxes entirely — their content frequently vanishes during parsing.

  • Why: tables impose invisible grid order on extraction; multi-column layouts make parsers interleave left and right text into gibberish; text-box contents often don't extract at all.
  • Check: after converting, select-all and paste into Notepad. If the Notepad version reads sensibly top-to-bottom, your structure is parser-safe. If lines are jumbled, keep simplifying.

Skill bars and rating dots go too

Those "Excel ●●●●○" graphics are invisible to parsers and meaningless to recruiters — replace each with plain text: "Skills: Excel (advanced), Power BI (intermediate)". The same applies to divider graphics and decorative lines; a blank line does the same job safely.

Step 3: Replace Creative Section Headings With Standard Ones (1 minute)

Rename anything clever to canonical headings parsers map reliably:

Creative headingUse instead
My Journey / Where I've BeenWork Experience / Professional Experience
What I Bring / My ToolboxSkills
Education & Learning PathEducation
Wins & HighlightsAchievements (or fold into experience bullets)

Order matters as much as names: Contact → Summary → Skills → Experience → Education is the sequence parsers expect, with student exceptions covered in our guide to the section order ATS parses best.

Step 4: Normalise Fonts, Sizes and Dates (1 minute)

  • Font: switch everything to one standard font — Calibri, Arial, Georgia or Times New Roman at 10–12pt body size. Unusual fonts can render as garbled characters in older parsers.
  • Dates: one consistent format everywhere, e.g., "Mar 2024 – Present". Mixed formats ("03/2024", "March '24") weaken timeline extraction.
  • Bullets: standard round bullets only. Custom symbols sometimes extract as junk characters mid-sentence.
  • No text inside images: if part of your resume is a picture (logos with embedded titles, scanned blocks), retype it as real text.

A worked example: the two-column conversion

Picture a typical designed resume: left column holds a photo, contact block and skill bars; right column holds experience. Converting it takes four moves:

  1. Copy your name and contact details to the top of the page as plain lines; delete the column frame.
  2. Replace each skill bar with a text line under a "Skills" heading, listing tools with proficiency words.
  3. Move the experience content directly beneath, keeping each role's title-company-date line intact.
  4. Delete the photo — UK and US norms exclude photos anyway (Indian formats too, for ATS purposes), and images add file weight while parsing as nothing.

Total elapsed time for this single biggest fix: about three minutes with Word's table-to-text converter doing the heavy lifting.

Step 5: Fix Job Title and Company Lines (1 minute)

Each role should follow one predictable pattern:

Job Title — Company, City | Mar 2024 – Present
followed by 3–5 achievement bullets.

Parsers split roles using title/company/date patterns; creative arrangements ("Company • awesome role since early 2024!") break the mapping, which distorts your computed years of experience in recruiter filters. If your internal grade differs from market terminology, mirror the posting's language — the honest way to do that is covered in our job-title mirroring guide.

Step 6: Decide docx vs PDF Correctly (30 seconds)

The safe default hierarchy:

  1. .docx when the portal accepts it — most reliably parsed across legacy systems.
  2. Text-based PDF when PDF is required or preferred — modern parsers handle these fine, and formatting stays fixed.
  3. Never scanned/image PDFs, Pages files without export, or Canva exports containing flattened design layers.

To check your PDF: try selecting its text with your cursor. If nothing highlights, it's an image and will parse as empty. The full trade-off analysis lives in our PDF vs Word for ATS breakdown.

One nuance worth knowing: some portals tell you which format they prefer — follow that instruction over any general rule, because the employer's system is the only one that matters for that application. When no guidance exists, .docx is the conservative choice; it has survived every parser generation since the 1990s and remains the lowest-risk option for legacy systems still common in large organisations.

Step 7: Verify Before You Submit (90 seconds)

Don't test on live applications. Two quick checks:

  1. Notepad test: select-all from your finished document, paste into Notepad, and read it top to bottom. Anything missing or scrambled here gets lost in parsing too.
  2. Automated check: run the file through JD2CV's free ATS Resume Checker, which flags parse-blocking elements and shows how your content reads to a machine — plus keyword gaps against a pasted job description.

For a printable pre-submission routine beyond this conversion, our ATS resume checklist walks every item in order.

Frequently Asked Questions About Converting Resumes

Will my converted resume look boring?

Plain, not ugly. Single-column resumes with clean fonts, bolded titles and clear spacing still look professional — they just also parse correctly. Remember the audience: a human spends seconds skimming; a parser either reads your content or doesn't. Design flourishes only ever help the former.

Should I keep both versions?

Yes — keep your designed original for direct emails, networking and LinkedIn attachments where humans open files, and your ATS-safe version for portals. Label them clearly (e.g., "Jane-Doe-CV-ATS.docx") so you never upload the wrong one. Length rules are identical for both versions; our one-page vs two-page analysis covers when to trim.

Do online converters do this automatically?

Some tools attempt automated restructuring, but none can judge context — deciding which right-column fragment belongs to which role needs human eyes. The seven manual steps above take ten minutes and produce a document you fully control. Automation helps more at the tailoring stage than the formatting stage; pairing the converted file with a tailoring pass against the job description is where scores actually move.

Do online converters do this automatically?

Some tools attempt automated restructuring, but none can judge context — deciding which right-column fragment belongs to which role needs human eyes. The seven manual steps above take ten minutes and produce a document you fully control. Automation helps more at the tailoring stage than the formatting stage; pairing the converted file with a tailoring pass against the job description is where scores actually move.

What if the job portal has its own form fields?

Fill every structured field exactly as your resume states them — same dates, same titles, same employer spellings. Parsers cross-check application forms against uploaded documents; mismatches read as errors or, worse, dishonesty. Where a field demands an exact format (dates as MM/YYYY, phone with country code), comply even when it differs from your document's style.

Does ATS formatting hurt my chances with human recruiters?

The opposite — clean structure helps humans too. Recruiters skim the same way parsers read: top-down, heading-guided. A single-column resume with bolded titles and consistent dates is easier for both audiences. The only thing you lose is decorative flair, which never decided a hire.

What Not to Worry About

A few things cause unnecessary panic but barely affect parsing:

  • Bold and italics. Styled text extracts normally; emphasis survives as emphasis. Keep using them for titles and keywords.
  • Standard bullet characters. Round bullets are fine; only exotic symbols cause junk-character issues.
  • Reasonable length. Parsers don't reject two-page documents — recruiters skim, systems index. Length rules are about human attention, not machine limits.
  • File name keywords. "Jane-Doe-CV.docx" is professional; the filename isn't a keyword channel. Don't stuff it.
  • Hyperlinks in body text. LinkedIn URLs extract fine; just display them as readable text (linkedin.com/in/janedoe) rather than hidden anchor text like "click here".

Key Takeaways

  • Contact details belong in the document body — never headers or footers.
  • Kill tables, columns, text boxes and skill bars; run the Notepad paste test.
  • Use canonical headings in canonical order: Summary, Skills, Experience, Education.
  • One standard font, consistent Month-Year dates, predictable title-company-date lines.
  • Prefer .docx where accepted; otherwise text-based PDF — never image-based files.
  • Verify with a free ATS checker before submitting, not after rejection.

Convert and Verify Today

Your next ten minutes decide whether a parser reads you at all. Apply the seven steps above, then confirm the result with JD2CV's free ATS Resume Checker — instant format scoring plus keyword matching against any job description, free to start.