> ## Content Index
> Fetch the complete content index at: https://trueapply.in/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# ATS resume formatting: check what the parser actually reads
- URL: https://trueapply.in/blog/ats-resume-formatting-check-what-the-parser-actually-reads/
- Published: 2026-09-28T13:22:29.000Z
- Updated: 2026-10-04T10:11:25.000Z
- Description: Check what the parser extracts from your resume, then review the document for clear, readable evidence.
- Author: TrueApply Editorial
- Tags: #agency-content-22-114a408d96ff8b0d

ATS resume formatting is about making your resume easier to read as structured information, not discovering a secret hiring score. A parser may miss a field without rejecting your application. Start by following the employer’s upload instructions, then check the extracted information wherever the application lets you review it.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

### Key takeaways

- Parsing and employer screening are separate steps: a resume that parses cleanly still needs to pass human review, and a parse failure does not automatically mean rejection.
- After uploading, inspect the extracted fields if the system offers a preview or edit screen; correct any missing or jumbled details so recruiters see accurate information.
- Follow the employer's accepted file format and size limit; for Greenhouse specifically, resumes larger than 2.5MB cannot be parsed.
- Keep your name and contact information in the main body of the resume, not in a header, footer, or text box, because Greenhouse documentation lists those placements as a parsing risk.
- Avoid graphics, photos, or word art in your resume file, as Greenhouse documentation identifies them as elements that may cause a parse to fail.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## How ATS resume parsing works

An applicant tracking system can extract resume text into candidate-profile fields. Greenhouse documents this as an import step: when parsing fails, the resume remains attached and the candidate’s details may need manual input. Its documentation also describes partial parses that need correction. That is different from an employer deciding whether to shortlist someone. The practical aim of ATS resume formatting is to make your information easy to extract and inspect, without treating clean extraction as a hiring guarantee.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## Common formatting issues that break ATS parsing

| Formatting issue                                                    | Possible effect in Greenhouse                                                      | Practical check                                                                                                 |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Resume file larger than 2.5MB                                       | Greenhouse Recruiting cannot parse the resume, so profile fields may remain empty. | For a Greenhouse application, check file size and remove unnecessary media without making text unreadable.      |
| Graphics, photos, or word art                                       | May fail to parse, leaving the resume attached but not extracted.                  | Use a clean, text-based layout without decorative graphics or embedded images.                                  |
| Resume uploaded as an image (e.g., scanned PDF or JPG)              | Can cause parsing issues because the text is not machine-readable.                 | Create a text-based document (.docx or .pdf) rather than scanning a paper resume.                               |
| Name and contact information in header, footer, or text box         | Can fail parsing, so the ATS may not capture your contact details.                 | Place your name and contact information in the main body of the document, not in a header, footer, or text box. |
| Company names without identifying words like Inc., Co., LTD, or LLC | May not parse correctly, potentially affecting work history extraction.            | Use the full legal company name as it appears on official documents, including suffixes if applicable.          |
| Incomplete job titles (e.g., Sr. Account Exec)                      | Can cause parsing issues, so the ATS may not recognize the role.                   | Expand abbreviations only when the wording accurately represents your real job title.                           |

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

2.5MB

Greenhouse resume parsing limit

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## File formats and technical specifications

Start with the file formats accepted by the employer. Greenhouse lists resumes uploaded as images rather than documents, such as .docx or .pdf, among possible parsing problems. A practical check is to see whether you can select and copy the text from your exported file. This is a useful inspection step, not proof that a particular employer’s parser will read every field correctly. Greenhouse’s documented parsing limit is 2.5MB; do not apply that number to every system. Follow the instructions on the actual upload form.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## Optimizing for both ATS and human readers

Use clear section headings and keep essential information in the main body of the document. Greenhouse lists contact details placed in headers, footers or text boxes as a parsing risk, alongside graphics and columned layouts. After uploading, review the extracted fields if that option is available. For a person reading the attachment, make your experience easy to scan and keep the wording accurate. When you revise the experience section, our guide to [resume bullet points without metrics](https://trueapply.in/blog/content-23/) explains how to describe scope without inventing numbers.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## Step-by-step: Make your resume ATS-friendly

1. Check the employer's accepted file formats and size limit before uploading. For Greenhouse, the parsing limit is 2.5MB, but other systems may differ.
2. Use a simple, single-column reading order. Avoid text boxes, sidebars, or complex tables that can confuse parsers.
3. Place your name, phone, and email in the main body of the document, not in a header, footer, or text box.
4. Write company names and job titles accurately. Do not add Inc., Co., LTD, or LLC if they are not part of the official name, and spell out abbreviations like 'Sr.' to 'Senior'.
5. After uploading, inspect the extracted fields if the system shows them. Correct any missing or scrambled data before submitting.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

This guide's parsing evidence comes from Greenhouse's public documentation, not from a Workday or Taleo test. Do not assume those systems share the same limits. Read the employer's upload instructions and inspect extracted fields wherever the system offers them.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## Illustrated layout choices to inspect

![Illustrative resume layouts compare separate text boxes and columns with contact details and clearly labelled sections in one reading order](https://trueapply.in/blog/media/trueapply-marketing/editorial/56/565fcbdc65f3cfb2454766f2947a43526de37c76a9910ece51862233baa012ff.png)

Conceptual layout comparison, not an ATS test result. Check extracted fields and follow the employer’s upload instructions. Image: TrueApply.

Does a parsing error mean my application was rejected?

No. In Greenhouse, an unparsed resume remains attached to the candidate, and profile details may need manual input. A parse failure is not itself evidence of rejection.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

Should I upload a PDF or DOCX?

Follow the employer's instructions. Greenhouse documentation notes that resumes uploaded as images rather than documents (such as .docx or .pdf) can cause parsing issues, so choose a text-based format unless the posting specifies otherwise.

Source: [support.greenhouse.io ↗](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in "External source: support.greenhouse.io")

## Sources

1. [https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse](https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse?ref=trueapply.in)