How Ashby Reads Your Resume
Ashby is one of the newest applicant tracking systems and one of the more candid: its public documentation names the exact reasons a resume fails to parse, and admits that its stronger parser is something an employer has to opt into. That last detail matters more than any formatting tip.
What Ashby accepts
Every line below links to the page it came from. Where Ashby does not publish a detail, this guide leaves it out rather than guessing.
When a resume is uploaded, Ashby creates a candidate profile, parses the resume details into the summary tab of that profile, and stores the original file in a viewable form beside it.
The original file sits next to the parsed summary, so a recruiter can always see what you actually wrote — but the summary is what gets read first.
What ATSPrep exports, and whether Ashby takes it
This is computed at build time by comparing our export formats to Ashby's published list — not written by hand, so it cannot drift out of date.
| ATSPrep export | Accepted by Ashby |
|---|---|
| Yes | |
| DOCX | Yes |
What trips people up here
The better parser is opt-in
Ashby offers “enhanced resume parsing”, which extends the range of supported languages and, in its own words, improves parsing for resumes with more complex layouts or formatting. It is an opt-in feature. Some employers on Ashby have it and some do not, and you have no way to tell which — so the sensible assumption is that you are being read by the standard parser.
Source: Ashby Docs — AI features and enhanced resume parsingA photograph of a resume will not parse
Ashby names this directly as a failure case: a file that is an image of a PDF, where someone photographed a document and converted it. It is a more common accident than it sounds, particularly when applying from a phone.
Source: Ashby Docs — bulk import optionsAn unusual layout defeats it
The second documented failure case is a file in a unique format, which Ashby describes as the candidate's details sitting somewhere the parser did not expect. Anything that moves your name and contact details away from the top of the first page is a candidate for this.
Source: Ashby Docs — bulk import optionsMarkdown is explicitly not supported
Ashby's file documentation calls out executable types and certain text-based formats such as .md as unsupported. Engineers who keep a resume in Markdown need to export before applying rather than attaching the source.
Source: Ashby Docs — candidate files and file categoriesThe size ceiling is generous
Ashby allows up to 50 MB, far above what a text-based resume needs. A limit that high means file size will not be your problem here — but it also means an enormous image-heavy export will upload happily and still parse badly.
Source: Ashby Docs — candidate files and file categoriesFormatting for Ashby
Export, do not photograph
Produce the PDF from the document itself. A scan or a photo converted to PDF carries no text layer, and Ashby lists exactly that as a parse failure.
Keep your name and contact details at the top
Ashby's second documented failure mode is details turning up somewhere unexpected. The top of the first page is where every parser looks first.
Assume the standard parser
Since enhanced parsing is opt-in, format for the weaker case: a single column, ordinary section headings, and no reliance on the layout to convey meaning.
Convert Markdown before you apply
If you write your resume in Markdown, export to PDF or DOCX. Ashby names .md among the formats it does not take.
Read your resume back the way Ashby will.
Guidance is worth less than evidence. Open the studio, export a PDF, and the X-Ray re-opens that exact file and shows you the text a parser recovers from it — in reading order, with anything it dropped marked. Free, no account, and your file is never uploaded.
Open the Studio →Ashby and your resume
What file types does Ashby accept?
For documents, PDF, DOC and DOCX, with a limit of 50 MB. Ashby's upload questions also accept images such as JPG and PNG and common video formats, but it explicitly does not support executables or certain text-based formats such as Markdown.
Why did my resume fail to parse in Ashby?
Ashby documents two reasons. The first is that the file is an image of a PDF, meaning someone photographed or scanned a document and converted it, leaving no text to extract. The second is that the file is in a unique format, where details the parser needs sit somewhere it did not expect to find them.
What is Ashby's enhanced resume parsing?
It is an opt-in feature that extends the range of supported languages — Korean and Hebrew are given as examples — and improves parsing of resumes with more complex layouts or formatting. Because employers have to enable it, you cannot assume it is on.
How big can a resume be in Ashby?
Up to 50 MB, which is far more than a text-based resume requires. Size is rarely the constraint on Ashby; whether the file contains real text is.
How the rest of them read a resume
Greenhouse
Greenhouse takes PDF, DOC, DOCX, RTF and TXT, and will not parse a resume larger than 2.5 MB. Its own support docs name what makes a parse fail — columns, contact details in a header, abbreviated job titles and more.
Oracle Taleo
Oracle publishes Taleo's accepted attachment formats but ships no resume parser of its own — parsing only works if the employer has enabled a third-party partner integration, so behaviour differs from one Taleo site to the next.
SmartRecruiters
SmartRecruiters accepts PDF, DOC, DOCX, RTF, JPG and PNG at 2 MB per file, and its CEO named Textkernel as the parsing engine — whose own documentation warns about PDFs more bluntly than any resume blog does.
Workable
Workable accepts PDF, DOC, DOCX, RTF, HTML and ODT for a resume, with a 5 MB ceiling — while other attachments on the same form are allowed four times that size.