LandOfferJob search
Resume Upload Failed? A Candidate Checklist Before You Retry
Locate the failed stage, preserve any submission evidence, then change one documented file or connection condition before a bounded retry.
A resume upload error calls for a pause before another click. First establish whether the attachment failed, the form could not read its contents, or the final application status is uncertain. Then check the resume field's stated requirements and change one condition before a retry. Repeated submission attempts can create more uncertainty than the original error.
If you are choosing a role while you repair the file, browse recently posted jobs on LandOffer and keep the employer's exact application destination. LandOffer publishes this guide and offers job-search tools. You can use the same checklist with your existing tracker and document editor; buying another tool is not necessary to diagnose an upload.
Name the stage that failed
An attachment is a file associated with a form. Parsing is software attempting to extract its contents into fields. Submission is sending the application to the employer. Those steps can succeed or fail separately. A filename visible beneath an upload box does not settle what happened after you pressed Submit, and blank extracted fields do not necessarily mean the file disappeared.
Write down what is visible before changing the page: the error's wording, whether the filename remains, whether a preview opens, whether required fields show errors, and whether a success message or application reference appeared. Save your own answer text locally if the form permits it. Avoid sharing screenshots containing identity, contact details or sensitive application answers with an unrelated troubleshooting service.
Use a short state label. “Attachment rejected before Submit” permits a file-focused retry. “Attachment present, fields incomplete” calls for field review. “Submit pressed, result unknown” calls for checking the candidate portal, visible receipt or an official support route before another submission attempt. A missing email alone does not resolve the third state.
Use the stage label to choose a repair that addresses the actual uncertainty. Compressing a file cannot confirm whether an application was received. Re-entering a name cannot repair an expired session. Refreshing a page may clear the error message and unsaved answers you need to understand the problem.
Read this field's requirements before using a general rule
Check the extension, maximum size, number of allowed attachments and any separate instructions for the resume and cover letter. A PDF accepted in one field may be unsuitable for another field that specifically requests DOCX. Keep the file extension honest: changing a name from .pages to .pdf does not convert the contents.
Greenhouse's candidate-upload documentation, updated August 19, 2026, lists DOC, DOCX, PDF, RTF and TXT with a 100 MB limit. That is a documented platform boundary, not permission to disregard a narrower requirement displayed by the employer. Read the actual field before deciding your file is within its limit.
A separate Greenhouse article about unsuccessful resume parsing, updated March 2, 2026, describes a 2.5 MB parsing limit in an administrator's candidate-import workflow. It also explains that an unsuccessful parse can leave the resume attached. Do not tell a candidate that every Greenhouse application upload has a 2.5 MB limit on that evidence.
Likewise, Lever's application-form configuration guidance discusses custom file-upload questions. A custom attachment field and the main resume field need not be treated as interchangeable. Platform help can explain a possibility; the employer's displayed instructions identify the task you are completing.
A completed file repair, with its limits visible
Keiko is applying to fictional Lumen Vale role LV-402. All employer details, file sizes and events in this example are teaching data. The resume field says PDF or DOCX, maximum 5 MB. Her six-page PDF includes large project screenshots and measures 6.2 MB. Before she has pressed Submit, the field rejects it and no filename remains attached.
Her first record reads: “LV-402; resume attachment rejected; 6.2 MB PDF; field maximum 5 MB; final Submit not pressed.” This is enough to choose a file repair. It does not diagnose an employer outage, a blocked account or a problem with every PDF.
Keiko keeps the original file, opens the source document and removes portfolio screenshots that do not belong in the resume. She retains the project description and a readable portfolio link. She exports a new PDF measuring 1.1 MB, opens it locally, checks each page and copies a passage into a text editor to check that the wording is selectable. The name, email, dates and project link remain correct.
She names the new version Keiko_Resume_LumenVale.pdf, with no confidential identifier in the filename. The simpler name helps Keiko identify the version; no evidence here establishes that punctuation caused the original failure. In this example, the visible size mismatch is the condition she changed.
Her second attempt attaches the 1.1 MB file. The field displays its filename and the preview shows the intended pages. She reviews any populated fields separately, then records “attachment accepted; application still not submitted.” That is a completed upload repair. It stops short of a fabricated successful application or hiring result.
The record lets you reconstruct the sequence: a stated requirement, a conflicting file property, a changed file, and an observed attachment state. If the smaller file had failed too, the same record would support escalation without claiming the original cause was proven.
Inspect the file without sacrificing its meaning
Open the exact file you plan to select, not the source document or an older export. Check that it has the intended pages, normal orientation and readable text. Confirm that conversion did not cut off contact information, break a link, omit a section or leave tracked changes visible. Reducing size is helpful only if the resume still communicates the evidence you intended.
If a preview fails, try opening the file locally. A local failure points toward the file itself; a local success leaves the application preview problem unresolved. Neither observation identifies the full cause. If an accepted attachment produces incorrect extracted dates or titles, correct the form fields from your source records where permitted rather than trusting the extraction.
Do not put an unsupported skill into a resume to make a parser happier. Do not convert the document to an image just because an image appears to upload: that can sacrifice selectable text and still violate the field's requirements. Use an allowed export format from the editor that already holds your accurate content.
Before using an online compressor, consider what it receives. A resume may contain contact details, employment history and other personal information. A local export with fewer unnecessary images may solve the size problem without transferring the document to another service. When a third-party tool is necessary, read its data handling terms and save the final file for your own inspection.
Check the connection only after preserving your work
An upload can also fail for reasons you cannot see from the error alone. The session may have expired, a connection may have dropped, or the form may have a temporary problem. Treat these as hypotheses unless the page provides more specific evidence.
After saving your own text and state record, confirm that ordinary pages load and that you are still on the employer-selected application route. If the form asks you to sign in again, use the normal sign-in flow. Do not treat a browser refresh or a second tab as a way to bypass an employer requirement.
If the employer's help instructions recommend another supported browser, try it with the same accepted file and record that single change. Keep the browser's security protections intact. Turning off every extension, clearing all account data or changing several network settings at once makes the result harder to interpret and may create new problems.
Record the condition changed before a second attempt. “Retry once after exporting within the stated size limit” is understandable. “Keep clicking until it works” is not a useful plan when you cannot tell whether Submit already succeeded. If the deadline is close, preserve evidence and use the official contact route promptly; keep the displayed deadline unless the employer changes it.
A complete escalation note when submission is uncertain
Consider a different branch of Keiko's fictional case: the file appears attached, she presses Submit, and the page stalls without displaying a result. The candidate portal shows no clear status. She should not reuse the earlier “attachment rejected” diagnosis. The uncertainty is now whether the application was received.
Here is a complete, unsent note for the employer's designated application support contact:
Hello, I am applying for Lumen Vale role LV-402. At about 2:20 p.m. Pacific on October 8, I selected a 1.1 MB PDF in the resume field and its filename appeared. After I clicked Submit, the page did not show a confirmation or reference number. My candidate portal does not currently clarify the status. Could you advise how to check whether this application was received before I retry? I can provide the error wording and browser version through your support process. Thank you, Keiko.
The note states what happened, identifies the role and asks a resolvable question. It does not demand that the employer remove a duplicate, claim the system lost the file or include a resume attachment by default. An employer may have a different contact process; follow it instead of sending this wording to an unverified address.
Keep a private record of the support request and any response. If the employer confirms receipt, mark the application accordingly and stop retrying. If it confirms no submission and directs another attempt, save that instruction and follow the verified route. If the status remains unknown, label it unknown rather than inventing a submitted date.
A phone upload needs the same evidence
On a phone, check which file the picker actually selected. A cloud-storage thumbnail may refer to an older export or a file that has not finished downloading. Open the chosen version, confirm its size and name, then return to the application's accepted-file instructions. If the picker cannot reach the file, that is different from a form rejecting a file after transfer.
Avoid selecting a screenshot of the resume because it is easier to find in Photos. It may look readable on your device while providing a different file type and different contents from the requested document. If transferring the inspected resume to a computer is practical, keep the same version and use the employer route there. Record the device change rather than concluding that mobile applications never work.
What to keep for the next application
Keep one accurate source resume, the inspected exported version and a short note about the requirement that mattered. You do not need a library of unexplained “final-final” files. Preserve enough version information to know which file is on which application, especially if you revise the resume after this incident.
For the next form, read the field again. Keiko's 5 MB example is not a limit you can carry to every employer. The upload and parsing documentation above describes different scopes, and public documentation is not a signed-in test of your particular application.
The decision is simple: fix a known file mismatch before retrying an attachment; check receipt before retrying a possible submission; escalate with observations when the cause remains unclear. Once you have an inspected file and a clear application status, browse recently posted jobs on LandOffer, verify each employer's instructions and reuse the tool setup that already works for you.