The application form has nine fields. Eight of them are fine. Then the prospect hits "Upload your proof of income" and disappears.
Your funnel analytics show a drop-off at step three. They don't show why. Most tools treat a file upload attempt as a single interaction — not a sequence of tries, failures, and quiet exits. So you're looking at a completion rate problem without a root cause.
What actually breaks at the upload step
File upload fields fail in ways that are invisible in your dashboard.
Size limits with vague or missing errors. Your server rejects files over 5MB. The user uploads their 8MB scanned PDF. The error says "Upload failed" — or says nothing at all. The user tries twice, gives up, leaves. You lost a qualified lead who completed 85% of your form. The form submit with no visible error pattern is its own category of quiet revenue leak, and file uploads are one of the most common places it shows up.
Mobile picker behavior. On iOS, the native file picker only surfaces files in the Files app by default. If your prospect wants to attach a document saved from their email client or a chat app, they can't find it. On Android, the picker behavior varies by manufacturer and browser. The upload works on Chrome desktop, silently fails on Samsung Internet, and QA never caught it because it wasn't in the test matrix. This is exactly the kind of mobile-only bug your QA misses.
Silent network failures. Large file uploads are vulnerable to dropped connections. If the transfer times out mid-upload and your form doesn't surface a clear retry state, the user may think it worked. They hit submit. The backend rejects because the file reference is incomplete. The form either throws a generic error or silently clears. Either way, the lead is gone.
Format restrictions that aren't stated upfront. The field accepts PNG only, but the label says "Upload ID document." The user uploads a JPG. The error appears after the upload attempt, not before. Users don't go back and re-read instructions — they leave.
Why your analytics miss all of this
Here's a structural problem: most form abandonment tools can't record what happens inside a file upload field. WPForms explicitly documents this — their form abandonment addon excludes file upload fields for privacy reasons. Most analytics platforms treat the field as a black box.
Your funnel might show that 65% of users who reach the upload step don't complete the form. But that 65% includes users who hit a size limit, users who couldn't find their file on mobile, users who got a silent network error, and users who were confused by format restrictions. Without being able to tell them apart, you can't fix the right thing.
What session replay actually shows you
Session replay records the full interaction sequence — not just field-level completion events. When a user fails on a file upload step, you can watch the exact sequence:
- Did they click the upload button once or multiple times?
- Did an error message appear, and was it visible in the viewport, or buried below the fold?
- Did they scroll back up to re-read the field label?
- Did the failure happen only on mobile sessions?
The filter to run in CloseTrace: segment sessions by "interacted with file upload field" AND "did not reach form submit." Sort by session length — longer sessions are users who tried more than once and gave up, not users who glanced and bounced. Those are your most qualified abandoners, and they're worth understanding individually.
For fintech and KYC flows where document upload is mandatory, the patterns are covered in more depth in how fintechs diagnose document upload failures.
Fixing size limits, mobile gaps, and silent errors
Size limit errors: Show the limit before upload, not after. Display it directly on the field label — "Upload PDF or JPG, max 10MB" — not in a tooltip. If you can, validate file size client-side on file selection so the user gets feedback before the upload even starts.
Mobile picker gaps: Test explicitly on iOS Safari and Samsung Internet with files stored in different locations. Add explicit accept attributes to the file input that match your actual allowed MIME types. If your users commonly have documents in cloud storage or messaging apps, add a link-based upload option alongside the file picker.
Silent network failures: Show an explicit progress indicator during upload. On failure, surface a retry button and name the error type ("Connection dropped — try again"). Log the failure event so it appears in your session recording data.
Format mismatches: State allowed formats and size limits directly in the field label, not in helper text or a sidebar tooltip. Validate format on file selection, not on submit — don't let a user spend 20 seconds uploading before telling them it's the wrong format.
One real limitation
Session replay captures UI behavior, not file contents. You'll see that a user clicked the upload button three times and then left — but not what file they were trying to upload or the exact server-side rejection reason. To get that, you need to cross-reference CloseTrace session timestamps with your backend error logs. The session timestamp gives you a precise window to search.
The next step: pull your last 30 days of session recordings filtered to your file upload form, segment by abandonment at the upload field, and sort by session length. If you see a cluster of sessions with two or more upload clicks and no visible error message in the replay, you've found the problem — and it's almost always a missing client-side error state, not a backend issue.