"Resume Could Not Be Parsed": What That Error Actually Means

The error that shows up after the spinner stops

You pick a file, the upload bar fills, there's a short pause while something in the background is presumably reading your resume, and then the page tells you it couldn't be parsed. No detail, no line number, just a vague prompt to try again or fill in your work history by hand. It's a strangely common moment in online job applications, and it's frustrating precisely because the error gives you nothing to act on.

The good news is that this isn't a mystery specific to you or to one unlucky company's website. Recruiting software vendors, the companies that actually build these parsing systems, document the common causes in their own support pages, because their customers' recruiters ask about it constantly too. Pulling from what several of them say, the causes cluster into a short, fairly predictable list.

It's usually a missing text layer

By far the most common root cause, across nearly every vendor's own troubleshooting guide, is a resume with no real text layer behind it: a scanned page, a photographed document, or a PDF that was effectively flattened into an image at some point in its history. To a human eye on screen, that file looks exactly like a normal resume. To a parser, there's no text to extract at all, because what looks like letters is actually pixels.

This is easy to check yourself before you ever hit submit. Open the file and try to select and copy a line of text from it. If nothing highlights, or if what copies out is blank or nonsense, you've found the problem, and it has nothing to do with your formatting choices, your wording, or your qualifications. It's a file-type issue, and it's fixable by re-exporting from whatever program created the original document rather than from a scanned copy of a printed page.

Oversized and oddly-formatted files

A few platforms document specific technical limits that cause an upload to fail outright. Greenhouse's own help center, for example, states that as of this writing, resumes larger than 2.5MB can fail to parse. That's a generous ceiling for a plain text document, a resume built from ordinary paragraphs rarely approaches it, but it becomes an easy limit to hit by accident if a file embeds a high-resolution headshot, a decorative background graphic, or was exported from a design tool at unnecessarily high resolution.

Heavy design elements cause a related but separate problem. Text boxes, embedded images used to render section headers, and dense visual templates can all interfere with extraction even when the underlying file size is fine, because the parser is trying to walk through content that isn't laid out as ordinary flowing text. More than one applicant tracking vendor's own troubleshooting documentation names this directly: a resume that looks more like a flyer than a document is a parsing risk on its own, independent of file size.

An uncommon or legacy file format can trip the same wire. Sticking to a standard, current PDF or DOCX export, not an obscure format, not a file saved from an old or unusual program, removes one more variable.

Language and encoding

This one is less talked about but shows up in more than one vendor's documentation: a resume written in a language other than what the parser defaults to handling can extract poorly or fail outright, depending on how the specific system was configured. If you're applying across borders or submitting a resume in a language other than the platform's default, and parsing fails where it wouldn't for an English-language file, that's a plausible reason, not a sign that something is broadly wrong with the document.

Sometimes it really isn't you

Not every "could not be parsed" error is about your file, though. Recruiting platforms occasionally have outages or service-side problems with their own upload pipeline, separate from anything a candidate did. If a form that normally works suddenly throws the same error on every file you try, including ones you know have a clean text layer, that's a signal the problem may be temporary and on their end. Waiting a few minutes, trying a different browser, or retrying later are reasonable next steps before you spend time re-exporting a file that was never the issue.

What actually fixes it

Once you've ruled out a platform-side outage, the fix is almost always the same regardless of which specific cause applies: re-export your resume as a current, text-based PDF or a standard DOCX file, directly from the program that created it, using a single-column layout without text boxes, embedded images standing in for text, or decorative backgrounds. Keep the file size modest. None of this requires guessing at which exact parser a given company runs behind its careers page, because the fix addresses the actual mechanism, a missing or obstructed text layer, rather than any one vendor's specific quirks.

If the form offers a fallback to manually enter your work history instead of relying on the uploaded file, that option sidesteps the error completely, at the cost of the time the parser was supposed to save you. It's a reasonable move if you're up against a deadline and don't want to spend it debugging a file export.

Where this connects to the bigger picture

A hard upload failure is actually the easiest version of a parsing problem to catch, because the system tells you outright that something went wrong. The harder, quieter version is a resume that uploads just fine, gives no error at all, and still loses your phone number, mangles your job history, or drops entire sections, simply because the parser handled a column layout or a stylized header differently than you expected. That failure mode doesn't throw a message. It just produces a worse version of your application that nobody flags for you.

That's the gap a parse-check is built to close, and it's a different question from "did this error happen," which ResumeReadout is built to show directly: run your actual file through, and see what a parser extracts from it, including whether there's a real text layer behind the page at all. That's something no amount of pasting resume text into a chatbot can tell you, because by the time you've pasted text somewhere, you've already done the extraction step by hand. The question a parse-check answers is whether your file survives that step on its own.

The bottom line

A "could not be parsed" error is annoying specifically because it's vague, but the underlying causes aren't mysterious once you know where to look. Vendor documentation across several different platforms converges on the same short list: no real text layer, an oversized or design-heavy file, an unusual format, or occasionally a language the parser isn't configured for, plus the rarer case of a plain outage on the company's side. Checking whether your file's text is actually selectable, keeping the format simple, and re-exporting from the original source document rather than a scan resolves the overwhelming majority of these without needing to know which specific system is on the other end of the upload button.

FAQ

Why does an application site say my resume "could not be parsed"?

Almost always, it's because the system couldn't extract a usable text layer or couldn't read the file at all. The most common reason is a scanned or image-only PDF with no selectable text behind it. Other documented causes include a file that's too large, an unsupported or corrupted file type, heavy design elements like text boxes or embedded images, or a resume written in a language the parser isn't set up to handle. Less often, the error is on the company's side: an outage or a temporary service problem, not your file.

Is there a file size limit that triggers this error?

On at least one major platform, yes. Greenhouse's own help documentation states that, as of this writing, resumes larger than 2.5MB can fail to parse. Other platforms set their own limits, and most aren't published anywhere a candidate can see. If your file is unusually large for a text document, often because it's embedding images or was exported at high resolution, that's worth checking before you assume the content itself is the problem.

How can I tell if it's my file or an outage on their end?

Try opening your resume and copying its text into a plain text editor. If the text comes out as a real, readable paragraph, your file likely has a working text layer, and the failure may be a temporary platform issue, worth retrying in a few minutes or a different browser. If nothing copies out, or what copies out is garbled, the problem is almost certainly the file, not the platform.

What's the fastest fix if I need to apply right now?

Re-export your resume as a standard DOCX or a text-based PDF (not a scan, not a print-to-PDF of a scanned page), using a single-column layout without text boxes or embedded images. Keep the file size modest, a resume is plain text and should rarely need to be more than a megabyte or two. If the form lets you type in your work history manually instead of relying on parsing, that option avoids the error altogether, though it costs you the time the parser was meant to save.

Keep reading

Or skip the reading and run the free parse-check →