An attachment in a form: selected, uploaded or still waiting?
Distinguish file selection from upload, and design per-file states, corrections, retries and confirmation of the right set.
Article language: English

In this article
A file has appeared on the list. It is easy to read a green mark beside its name as confirmation. Yet the browser may have only recorded the selection, and a document that reached the server may still be waiting to be accepted into the case. For the person sending it, this is one task. The design needs to show its stages honestly.
Imagine a fictional workshop making exhibition display cases. A customer attaches a drawing, a photograph of the site and a file describing the exhibition. The photograph turns out to be too large, a newer drawing replaces the first and the connection interrupts the description upload. In the end, the team needs the right set. The customer wants to know what remains to be done without starting the whole request again.
First decide what set allows work to begin
Do not start by drawing a dashed border. Establish why the workshop needs the documents. The drawing may describe dimensions, the photo the conditions at the site and the description the type of exhibits. Three files are not interchangeable evidence of the same task. A missing drawing has a different consequence from a missing additional photograph.
Consider a single document that meets several needs. The customer may have all drawings and the description in one PDF. If the form requires three separate files only because the mock-up has three boxes, it creates needless work splitting the material. Agree with the workshop whether a combined document is acceptable and how to indicate what it contains. If separate items are needed for the later workflow, explain that before selection with instructions matching the recipient's real need.
Give each material type a recognisable purpose. “Display case drawing, if you already have one” helps someone decide what to select. “Attachment 1” leaves that work to the customer. When material is optional, explain what can happen without it. The workshop may prepare questions for a conversation but need measurements before a proper quote. The form should reflect that distinction.
Agree file limits with the person responsible for receiving and storing documents. The designer needs to know accepted formats, size, number of items and the checking process. These determine the interface instructions and states. A sentence beside a button does not itself enforce a server limit or establish that content is safe.
Show conditions before file selection. Tell customers whether they may attach several documents and whether a limit applies to each file or the whole set. If compressed folders are not accepted, say what to provide instead. Explain that condition before someone spends time uploading.
In contact form design (in Polish), attachments are part of a larger task. Preserve the case description, contact details and earlier answers. A faulty photograph is no reason to erase a correctly entered question about the display case.
Each file needs its own history
After selection, show an identifiable item: name, size and state. If the document has a particular role, retain that too. “Drawing - design-03.pdf” says more than “design-03.pdf” alone. Someone returning to the form after a short break should not have to reconstruct the order in which files were added.
Also handle cancelling the selection itself. The customer presses “Change drawing”, opens the file picker and closes it. Check that the previous item remains on the list and its state has not changed. Deciding not to search for a newer version must not look like deliberately removing the old one. In a trial, ask the person which document they now intend to send. The answer quickly shows whether the control's behaviour is understandable.
A long name should still distinguish the version. If two documents differ at the end with “approved” and “draft”, hiding that very ending behind an ellipsis removes the most useful information. Make the full name available on a phone and without hover. A thumbnail may help with a photograph but does not replace identification of a document.
Distinguish selection, upload and readiness to submit the request. For this example, working state names might be selected, uploading, checking, ready and needs correction. Agree these with the system's actual behaviour. Each name should correspond to an observable event, not a percentage drawn to reassure the customer.
If uploads begin automatically, explain that at selection. If the final button starts the transfer, show the prepared list beforehand. In both cases, make clear whether “Remove” deletes a local selection or a document already associated with a draft. People should not discover the difference by an accidental click.
Replacing the drawing needs an equally clear decision. First the customer selects the new version, then sees that it is ready and receives confirmation of the replacement. If the new file fails, they need to know whether the previous one remains with the request. Agree this explicitly. Two similar names and a single cross do not explain which design the workshop will receive.
Reproduce replacement while two transfers run at once. The customer selects a corrected drawing before the previous upload ends; in the trial the older file arrives later. Agree with the implementer how the system preserves the intended replacement, and show the accepted version in the interface. Message order alone does not explain the customer's intent. After both attempts, the summary should identify the drawing actually chosen for further work.
Test files with identical names too. Their contents may differ, particularly when downloaded from two messages. If the system allows both, the interface needs another way to distinguish them. If it identifies a duplicate, explain what was omitted. A name alone is not sufficient reason to silently replace one version with another.
An error should point to a specific action
GOV.UK's File upload guidance distinguishes messages for the wrong format, excessive size, an empty file and a failed upload. It is a useful reference: the action available to the user depends on the problem.

In our fictional case, an oversized photo needs replacement or reduction. An interrupted description transfer needs a retry. A missing drawing may require selecting the right document. “Invalid file” distinguishes none of these. The customer must discover what the system wants.
Show the error beside the affected item. With a larger set, a summary leading to the problem document also helps. Other valid files should retain their states. If one transfer fails, do not mark the whole list empty or make the customer find a drawing already accepted again.
State the limit and a possible next step. “The photo is 18 MB; the limit is 10 MB. Choose a smaller file” is a working example; actual numbers must come from your agreed limits. A service outage needs a different message. Editing a document will not repair an unavailable server.
When the cause is unknown, preserve that uncertainty. Do not declare the file corrupt merely because a request failed. Explain what the user can retry and which data has been retained. If you offer another contact route, it should reach someone able to handle the same case.
The progress bar has reached the end. What next?
MDN's upload documentation describes loadend as occurring after a transfer ends whether it succeeded or failed. That is a specific technical boundary: the end of a stage is not, on its own, evidence of success.
For the workshop's customer, what happens next matters. A document may have arrived but still need checking or association with the request. If those operations really exist, they need separate states. Do not leave the bar at 99 percent while an entirely different operation happens. The user cannot tell whether to wait, refresh or start breathing exercises.
Show numerical progress for the scope you can actually measure. When the end of a wait is unknown, naming the current action and providing a way to leave safely may be better. The design of a long-running task (in Polish) covers the return: where to find the result and what to do if the original tab was closed.
The submit button must take the set's state into account. In our example the drawing is ready, the photo needs replacing and the description awaits retry. Decide whether a request may be sent without the photo. If so, the customer must choose that knowingly. If not, explain the exact missing item rather than leaving a disabled button without a word.
Preview and return should not mix up versions
A thumbnail helps check whether the correct location was photographed. For a multi-page document, the customer may need more than the first page. Before adding preview, agree its scope: which formats it supports, whether it shows the selected file and how to return without losing the form. Keep the name of the open version visible.
For a phone photograph, check selection too. A customer may have several nearly identical shots and recognise the correct one only in a larger preview. Let them return to and replace that specific item. Check that a portrait image and long name do not obscure the controls. This should be viewing the selected material, not a second, harder task of finding how to close the preview.
HTML and SVG files with active content (in Polish) require understanding what opening them may execute. A form accepting material need not automatically offer a preview of every accepted format. Choose a checking method suited to the file's actual workflow.
If a request can be saved, distinguish retention of form data from retention of attachments. Someone returning the next day should see which items are still available. “Draft saved” must not hide the need to select every document again. This is one condition of a form completed over several sessions (in Polish).
A similar order helps when preparing material for an audit (in Polish): the recipient needs to recognise the document's role and version. Retain that information for the workshop team too. The list the customer accepted before submission should be comparable with the material actually associated with the case.
Accept the same set on both sides
Prepare a trial with three documents having clearly different roles. Replace one, remove another and interrupt the upload of the third. Then return to the form and try to finish the case. Record what the person sees for each file and which material the workshop ultimately receives. Check the document's path, not only an elegant list.
At the workshop, ask a second person to find the drawing the customer approved. They should recognise it without guessing from the download date. Check that role and version information survived the handoff and that a removed item did not return in an automatically prepared package. If the team receives only a case notification and files are elsewhere, follow that link too and establish that it leads to the correct case.
Repeat key actions on a phone and with a keyboard. A user should be able to identify an item, start a correction and find the result. Do not rely on an unlabelled cross that appears only on hover for removal. When the list changes, check where interaction continues: after removing a file the customer still needs to know where they are.
Finally, compare the summary with the back-end state. Confirmation after submitting a form (in Polish) should refer to an operation actually accepted. If some documents did not arrive, a green screen must not claim the set is complete. It is better to identify the missing item and preserve the case number than to make the customer submit another request saying “I do not think the previous one went through”.
For a conversation about website design at Aeneia Design, prepare several typical documents and one difficult case. That will help establish the required states and the boundary of the form's work before choosing the control's appearance. A well-designed list answers a simple question: this file is correct, this one is still waiting and this one needs my action.







