Provider limits cited here are examples from linked documentation checked for this article. They are not limits for every employer or for ResuMateAI.
Quick Takeaways
Read the portal's stated limit and error message, inspect the actual file size and format, and export a lighter copy from the source. Reopen it before retrying. Attachment limits, preview limits, and parsing limits can differ, so successful upload alone is not the final check.
- Use the limit shown by the actual application, not a number copied from another website.
- Remove unnecessary image weight before removing relevant resume evidence.
- Check upload completion, the saved attachment, and any populated profile fields separately.
Identify which limit or stage has failed
Write down the error message and the stage where it appears. A file rejected before upload is different from an attachment that uploads but does not preview, or one that previews while the profile stays empty. Check the filename extension and the actual document type as well as size.
Greenhouse's published guidance illustrates why the stages matter: its candidate-upload documentation describes a larger attachment allowance than its separate resume-parsing guidance. Treat those as distinct product capabilities. Do not turn either figure into a universal ATS size rule, and do not assume the Bot uses the same limits.
Reduce document weight at the source
Look for full-resolution photos, screenshots of text, scanned certificates, decorative backgrounds, and images pasted several times. A resume is not usually the right place to embed an entire certificate portfolio. Keep useful evidence in an appropriately shared portfolio and link it clearly when the application permits links.
Export a copy after removing unnecessary images. Keep readable body text and the project descriptions intact. Compressing an already small text-only PDF repeatedly is unlikely to solve an unrelated format or network problem. Avoid making the text microscopic just to chase a smaller number in the file properties.
| Observed problem | First test | Do not assume |
|---|---|---|
| File exceeds the displayed limit | Export without unnecessary images | Every attachment limit is the same |
| File is small but rejected | Check supported format and file integrity | Smaller always means accepted |
| Attachment works, fields are blank | Inspect parsing and correct profile fields | Upload completion means parsing succeeded |
| Upload stalls for multiple valid files | Check portal status and connection | The resume wording caused a network error |
Try it on your resume
Get feedback on your own resume
Open ResuMateAI in Telegram, tap Start, and send your resume. Add a job description when you have one.
3 free credits for new users. PDF or DOCX. No card needed to try. A job description is optional.
Opens @ResuMateAIBot in TelegramPreserve a reproducible submission copy
Save a distinct lighter version, reopen it, and inspect every page. Confirm that image removal did not erase a contact line that had been stored as a picture or remove a project diagram that was the only explanation of your work. Replace essential information with readable text rather than simply deleting it.
Keep the original source and a record of which version was submitted. If the portal supplies an attachment preview or downloadable copy, verify that the expected version is present. Repeatedly attaching similarly named files without checking the result can leave an older document in the final application.
Escalate a portal issue with useful, limited information
If a valid file still fails, use the employer's support route. Include the time, browser, file type, approximate size, and exact error. Redact private information from screenshots. Do not send a password, identity document, or unrelated personal file unless a legitimate application process explicitly requires it.
For ResuMateAI, read the current file limit shown by the Bot and choose the correct service. PDF and DOCX analysis differs from the English-DOCX rewrite preview. Reducing size cannot make an unsupported input type supported. Keep employer uploads and Bot uploads as separate troubleshooting cases.
How to use this guide on a real application
Use this when an upload is rejected, stalls, produces no preview, or creates an incomplete application profile.
Once the upload works, return to the actual job requirements. Keep a short record of the repaired file's size and type so a later design revision does not reintroduce the same technical problem.
Application checklist
- Read the exact portal message and displayed limits.
- Check real file type and size.
- Remove unnecessary images in an editable copy.
- Reopen and inspect the lighter export.
- Confirm both the saved attachment and profile fields.
What to avoid
- Using one provider's limit as a universal standard
- Deleting strong project evidence before inspecting images
- Retrying repeatedly without checking the saved attachment
References and editorial notes
We consulted these public resources while preparing this guide. Resume examples on this site are illustrative and should be adapted to your real experience. Read how ResuMateAI prepares and reviews its guidance.
- Greenhouse: supported candidate uploads
Attachment acceptance is a separate issue from text parsing.
- Greenhouse: unsuccessful resume parsing
Documents a product-specific parsing-size constraint.
Try it on your resume
Get feedback on your own resume
Open ResuMateAI in Telegram, tap Start, and send your resume. Add a job description when you have one.
3 free credits for new users. PDF or DOCX. No card needed to try. A job description is optional.
Opens @ResuMateAIBot in Telegram