Your files never leave your device — every tool runs inside your browser.See the proof

Organize

Optimize & Repair

Convert

Edit & Sign

Image tools

Start free

How to Make an ATS-Friendly CV PDF That Software Reads Before Humans Do

WPPR TeamPublished 10 min read2,347 words

Applied to dozens of jobs and heard nothing back? The problem might not be your experience — it might be the file. Many mid-size and large employers use an applicant tracking system (ATS): software such as Workday, Greenhouse, Lever, iCIMS or Taleo that receives CVs, extracts their text and organises it — sometimes ranking candidates by how well they match the job — before any person sees them.

If the system can't read your CV properly, a recruiter may see it incomplete or garbled, or it may never appear when they search for a skill you actually have. This guide explains how ATS software reads a PDF, and how to design, save and compress your CV so it's read correctly.

Key takeaways
  • Submit a text-based PDF saved from Word or Google Docs — not a scan, not a heavily compressed file.
  • Test it: if you can't select and copy the text cleanly, an ATS probably can't either.
  • Avoid multi-column layouts, complex tables and text inside images; don't put contact details only in the header.
  • Use standard section headings: Experience, Education, Skills.
  • If you must shrink it, use light compression only, e.g. Compress PDF for job applications.

How does an ATS "read" your CV?

When you upload a CV, the system typically:

  1. Extracts the text from the file — much like you selecting and copying it.
  2. Parses the structure: identifies your name and contact details and sections like Experience, Education and Skills, then pulls out job titles, employers and dates.
  3. Fills a candidate profile in its database with that information.
  4. Enables search and filtering: a recruiter searches for "financial analyst", "Excel" or "SAP" and sees CVs containing those terms.

Step one matters most. If text extraction fails, nothing that follows can help. With PDFs, that failure has specific, avoidable causes.

The two-minute test: can an ATS read your CV?

Before anything else:

  1. Open your CV PDF.
  2. Press Ctrl+A (Cmd+A on Mac) to select all, then Ctrl+C to copy.
  3. Paste into a plain text editor (Notepad, TextEdit in plain-text mode).
  4. Read the result.
What you see What it means
Clean text in the right order Great — your CV is readable
Nothing copied Your CV is an image; the ATS will read almost nothing
Jumbled lines from two columns interleaved Multi-column layout is confusing extraction
Odd symbols or broken characters Font or encoding problem
Missing parts, like your name or email Information sits in images, text boxes or the header

What you see in the text editor is close to what the system sees. If it's messy for you, it's messy for the ATS.

Safe formatting: do's and don'ts

Do

  • One column, read top to bottom. The most reliable layout there is.
  • Standard section headings: Experience (or Work Experience), Education, Skills, Certifications. Avoid creative headings like "My Journey" or "Where I've Been".
  • Common, clean fonts: Arial, Calibri, Helvetica, Georgia, Garamond.
  • Consistent dates: "01/2022 – 06/2024" or "Jan 2022 – Jun 2024" — the same format throughout.
  • Simple bullets (•), not decorative symbols.
  • The job ad's own terms: if it asks for "project management" and "Power BI", use those exact words where they truly apply, not distant synonyms.

Don't

  • Don't make your CV an image — don't design it in a graphics tool and export a picture, and don't print and scan it.
  • Don't put key details inside images or icons. A phone icon next to the number is fine; the number itself must be text.
  • Don't rely on complex tables for layout. Simple tables may parse, but it's an unnecessary risk.
  • Don't put your name and contact details only in the header. Some systems ignore headers and footers.
  • Don't use floating text boxes in Word; they can be extracted out of order or skipped.
  • Don't load it with graphics like skill bars or rating dots. Software doesn't understand that four stars means "advanced".

PDF or Word?

A common question with a simple answer: do what the job posting or portal asks. If they want DOCX, send DOCX. If they want PDF, send PDF.

If both are allowed, a text-based PDF reads well in most modern systems and has the advantage of looking identical on every device, whereas a Word file can display with different fonts and margins on the recruiter's machine. The key is that the PDF comes from "Save as PDF" in your writing app, not from printing and scanning.

How to save your CV as a proper PDF

Microsoft Word: 1. File → Save As. 2. Choose PDF as the file type. 3. Pick "Standard (publishing online and printing)" for the best text quality. 4. Under Options, enable "Document structure tags for accessibility" if available — it helps some systems understand structure.

Google Docs: File → Download → PDF document.

Canva and design tools: if you designed your CV there, make sure text stays text when exporting and run the copy-paste test. Many attractive templates use columns and elements that confuse ATS. Keep a simple version for online applications and a designed version to send directly to a person.

File size: how big should it be?

A one- or two-page text CV without big images is usually tiny — tens to a few hundred KB. Most portals accept several MB, so you usually won't need compression.

If your CV is large, the usual causes are:

  • A headshot at full camera resolution. Resize it before inserting with Compress image; 400 px wide is plenty for a small photo.
  • High-resolution logos of employers or universities.
  • Coloured backgrounds and designs saved as images.
  • Fully embedded fonts, especially some large decorative fonts.

If you need to shrink it, use Compress PDF for job applications on light, or type the portal's limit into the target size field.

Never compress your CV with "strong"

Strong compression turns every page into an image. Your CV will look perfect to your eyes — but the text disappears for the software. It will fail the copy-paste test and may be filtered out without anyone reading it. This is one of the most damaging and least visible mistakes.

If the portal's limit is tiny and light compression isn't enough, fix the source: remove or shrink the photo and export from Word with "Minimum size". More approaches are in How to compress a PDF without losing quality.

Keywords: matching the job ad without stuffing

ATS lets recruiters search by specific terms. If they search "cost accounting" and the phrase isn't in your CV, you may not show up despite having the experience. But keyword stuffing hurts you with human readers. A balanced approach:

  1. Copy the job ad into a document and highlight the skills, tools and qualifications it asks for.
  2. Group them: technical (Excel, SAP, Python), professional (budgeting, team leadership), credentials (CPA, PMP, a specific degree).
  3. Mark only what you genuinely have. Don't add skills you lack; interviews expose them.
  4. Use their wording: if the ad says "project management", don't write "coordinating initiatives". If it says "Microsoft Excel", write it in full; you can add the short form too.
  5. Put keywords in context: "Built the annual budget for a 40-person department using Excel and SAP" beats a bare list of "Excel, SAP, budgets".
  6. Include a clear Skills section gathering core terms, so both software and humans see them at a glance.

A suggested ATS-friendly structure

``` FULL NAME Target job title City, Country | Phone | Email | LinkedIn URL

PROFESSIONAL SUMMARY 3–4 lines on your experience and what you offer, using the ad's language.

EXPERIENCE Job Title — Company — City 01/2022 – Present • Achievement with numbers where possible • Another achievement

EDUCATION Degree — Major — University — Graduation year

SKILLS Skill 1, Skill 2, Tool 1, Tool 2

CERTIFICATIONS Certification — Issuer — Year

LANGUAGES English (native), Arabic (professional) ```

This simple structure parses in virtually any system and still looks elegant to people with a good font and balanced spacing.

The most common design mistakes (and why they fail)

Mistake Why it confuses the ATS Alternative
Two columns: skills left, experience right Lines get read across both columns and mixed One column; skills as their own section
Name as artwork or a logo Not extracted as text Name as plain text in a large font
Skill rating bars No textual meaning Write the level: "Advanced", "Intermediate"
A table for dates and titles Cell order can scramble Simple text lines
Icons only (☎ ✉) with no labels Icons mean nothing to software Write the value clearly as text
Decorative fonts May not embed well and come out as symbols Standard fonts
Dates like "two years ago" Experience can't be calculated Month and year

Two versions: one for software, one for people

If you're a designer or in a creative field, you may want a visually distinctive CV. The professional solution is to keep two:

  • ATS version: simple, single column, all text. Upload this to portals.
  • Designed version: shows your style. Send it directly to a person, bring printed copies to interviews, or include it in your portfolio.

Same content, different formatting. Update both whenever you add experience.

What the recruiter sees after the ATS

Once the system extracts your data, recruiters usually see a structured summary, then open your original file if it catches their interest. Now human reading matters, and the first scan often lasts only seconds. So:

  • Put the most important information in the top third of page one: target title, summary, most recent role.
  • Start bullets with achievement verbs: reduced, launched, led, delivered.
  • Use numbers: "Cut costs by 12%" beats "Helped reduce costs".
  • Leave white space: a cramped CV tires the eye even if the ATS reads it perfectly.

Bilingual and non-English CVs

If you're applying in multiple markets — say, English and Arabic — a few specifics:

  • Run the copy-paste test on every language. If Arabic letters come out disconnected or reversed, switch to a modern Unicode font such as Arial, Tahoma, Segoe UI or Dubai.
  • Don't put two languages in side-by-side columns on the same page; it scrambles extraction. Use separate files, or one language section after the other.
  • Spell your name consistently across all documents, matching your passport.
  • Use one digit style throughout — Western digits (0123456789) are safest for search.
  • Match the language of the ad: if the posting is in English, send an English CV, even for a company in a non-English-speaking country.

File name and properties

The file name is shown to recruiters, and sometimes to the system:

  • Good: Jane-Doe-Financial-Analyst-CV.pdf
  • Bad: cv final final 2 (1).pdf

Use letters, numbers and hyphens; avoid spaces and symbols. Some older systems choke on long or special-character names.

File properties (metadata): every PDF has Title and Author fields. Some systems and PDF readers display the Title instead of the file name. If yours says "Document1" or a template's name, it looks careless. Fix it with Edit PDF metadata: set the title to "Jane Doe – CV" and the author to your name.

Attachments: certificates and reference letters

If the job asks for supporting documents, you have two options:

  1. Separate files: CV alone, certificates in another file. Best for ATS, because your CV stays clean text.
  2. One file: if only one upload is allowed, put the CV first and merge certificates after it with Merge PDF. Scanned certificates won't be machine-read — that's fine, as long as the CV pages remain text.

When compressing the merged file, beware: strong compression will turn your CV pages into images too. Use light, or compress the certificates file alone before merging.

Final checklist before applying

  • Text-based PDF that passes the copy-paste test.
  • One column; no text inside images.
  • Name, email and phone in the body, not only the header.
  • Standard, clear section headings.
  • Consistent date format.
  • Key terms from the job ad present, where they genuinely apply.
  • Size within the portal limit, without strong compression.
  • Clear file name; correct Title in document properties.
  • Spelling, numbers and LinkedIn or portfolio links checked.

FAQ

Does every company use an ATS?

No. Small companies often review CVs by hand from email. But larger employers, recruitment agencies and government job portals widely use systems to receive and organise applications. ATS-friendly formatting never hurts with humans, so it's worth doing every time.

Does a photo hurt with ATS?

The photo itself doesn't stop text extraction, but it increases file size and may display oddly. In the US and UK, photos are generally discouraged for anti-discrimination reasons; in parts of Europe, the Middle East and Asia they're common. Follow local norms — and shrink the photo if you include one.

Can ATS read non-English CVs?

Modern systems generally support many languages, provided the text is properly encoded. The copy-paste test reveals problems early.

How many pages should a CV be?

There's no fixed rule. One to two pages for most people; longer for extensive or academic careers (where a CV can run many pages). Relevance matters more than length.

I compressed my CV strongly and already applied. What now?

If the portal lets you update your file, upload a text version. If not, send the text CV directly to the recruiter if you can find their email, mentioning the role you applied for.

Is WPPR safe for my CV?

Yes. Compression, metadata editing and merging all happen in your browser; your CV is never uploaded to a server.

Bottom line

An ATS doesn't see your CV the way you do — it sees the text it can extract. Make that text complete and well ordered: single column, standard headings, a text PDF saved from your writing app, and never strong compression. Always run the copy-paste test before you hit submit.

Prepare your CV now with Compress PDF for job applications on light, and fix its title with Edit PDF metadata.

Sources

W
WPPR Team

The WPPR team builds PDF tools that run entirely in your browser and tests every method in these guides on real files before publishing.

Related articles