Skip to main content
Orilami
Choose a résumé PDF to begin.

ATS Resume Sanitizer: before and after

An illustration with sample files; your own files show their own results.

BeforeRésumés the parser misreads
  • Two columns read straight across

  • Contact lost in the header

  • Skill bars and icons

AfterRebuilt so every parser reads it
  • One clean column

  • Contact moved into the body

  • Plain text, nothing lost

Workday Resume Checker: Test How Workday Reads Your Résumé

Many employers collect applications through Workday, and a parser reads your résumé before a person does. Multi-column layouts, tables and text boxes are commonly reported to come out scrambled: the parser reads straight across the page, so a sidebar of skills can land in the middle of a job description.

The tool above flattens the layout into one reading order, repairs broken characters, and rebuilds the résumé as a clean, searchable PDF, DOCX or Markdown file. Its audit projects the result onto five ATS pipelines, Workday included, so you can see what changed. It is a local simulation built from documented parsing weaknesses, not a connection to Workday, so it shows risk but cannot promise a pass.

This is the ATS Resume Sanitizer set up for one case. See everything it does →

ATS Resume Sanitizer

Applicant Tracking Systems read a résumé as one linear text stream, and they fail in predictable ways: columns interleave, ligatures and broken fonts turn into garbage, content in form fields or images is dropped, and headers get truncated. The ATS Resume Sanitizer rebuilds your résumé as a single-column, machine-readable document, entirely in your browser. Your file never leaves your device.

What it does

  • Spatial linearization: an XY-cut engine finds column gutters and block gaps and flattens columns, sidebars and visual tables into one reading order.
  • Glyph & CMap repair: expands ligatures (fi, fl, ffi…), neutralises Private-Use-Area characters from broken CMaps, and folds exotic bullets, dashes and quotes to plain equivalents.
  • Artifact stripping: the output is rebuilt from text only, so images, skill bars, decorative vectors, form fields and annotations are gone by construction.
  • Semantic restructuring: content is sorted into canonical sections (Contact, Summary, Experience, Skills, Education, Certifications…).
  • Dual-target output: a searchable text PDF plus an unstyled DOCX and Markdown, ready for any parser.
  • Headless ATS audit: a built-in mock parser scores machine readability and projects it onto five pipelines: Workday, Taleo, Greenhouse, Lever and iCIMS.

A note on PDF/A

The PDF is a clean, searchable text PDF with ISO core fonts and a classic cross-reference table, which covers everything an ATS relies on. It is deliberately not stamped as PDF/A-1b/2b: true conformance needs colour profiles, XMP metadata and a validating toolchain that a client-side tool cannot guarantee. You get a document that parses correctly, not a badge it cannot verify.

Frequently asked questions

Does this connect to Workday or test against a real Workday account?
No. Nothing is sent to Workday or any other system. The audit is a local simulation: it applies Workday's commonly reported parsing weakness, multi-column interleaving and mis-read tables, to your document's structure and reports whether that risk is present. It shows risk, not a guaranteed result.
What does Workday's parser struggle with in a résumé?
Layouts that put text side by side are the usual culprit. Columns, sidebars, text boxes and layout tables can be read across the page instead of down it, which mixes unrelated lines together. The sanitizer detects the columns, flattens them into one reading order and reports how many it found.
Should I submit a PDF or a DOCX to Workday?
Either can work when the file is built cleanly. What matters is a single column, real text rather than an image, and standard section headings. This tool exports a searchable PDF and a DOCX from the same cleaned content, so you can choose whichever format the application asks for.
Is my résumé uploaded anywhere to be checked?
No. The whole check runs in your browser and the file is never uploaded. Previewing and checking need no account; an account is needed only to spend tokens when you download the result.
More questions about Orilami →

ATS Resume Sanitizer at a glance

Key facts about ATS Resume Sanitizer: where it runs, what it costs, what it accepts and produces, and its limits.
Where it runsEntirely in your browser. Files are never uploaded.
Cost280 tokens per resume (about $2.80 at the base rate)
AcceptsPDF
ProducesA rebuilt, machine-readable PDF plus DOCX and Markdown versions, and a conformance audit scored against five parser families.
BatchOne at a time.
Account neededOnly to spend tokens. Browsing and previewing are free.
What it does not doIt fixes how a resume is structured and parsed. It does not write your resume or judge your experience.

Local processing vs. cloud tools

How Orilami compares with the typical online tool that uploads your file to its servers.

Orilami local processing compared with typical cloud tools on file privacy, edit and delete safety, speed, and pricing model.
CriterionOrilami (runs locally)Typical cloud tools
File privacy0 bytes leave your device. Files are processed in your browser's memory.Files are uploaded to external servers, where they may be logged or retained.
Edit & delete safetyThe résumé is rebuilt from clean text, so hidden layers, graphics and encoding noise are not carried over.Your original and the rebuilt copy often sit on their servers for a while after you leave.
Speed & performanceInstant: runs on your device, with no queue and no upload or download wait.Depends on your connection and on server load.
Pricing modelPay per use with tokens. No mandatory monthly subscription.Typically a recurring monthly subscription that adds up.

The cloud column describes upload-based online tools in general. Individual services differ.