File upload
Uploading a file might seem simple, but for many users, it’s where doubt creeps in. They might be under pressure, unsure of what’s needed, or anxious about making a mistake.
In DWP file uploads often appear in services that support people at difficult points in their lives: providing evidence for a claim, an assessment, or a change in circumstances. That context makes clarity and reassurance especially important; the interaction may be small, but the stakes rarely are.
What this research is
This isn’t a finished pattern or a set of rules. It’s an open piece of work, shared early to invite collaboration, spark discussion, and help us get to better answers together.
Because we don’t yet have a complete component or pattern for file uploads, we’ve also included a practical checklist. It’s not a rulebook: it’s a set of prompts to help teams think through design decisions, spot potential issues, and shape smoother experiences while our guidance develops.
What we’ve done so far
We’ve focused on understanding how file uploads work in existing services across DWP and where things might fall short for both users and teams. That’s meant digging into:
- How teams handle uploads in live services
- Where things feel unclear, inconsistent or unsupported
- Where uploads appear in the journey
- What evidence we ask for and how we help users provide it
- How other departments across government are tackling similar challenges
We also looked at the broader context of how uploads fit into user journeys and what happens around them:
- Do people know straight away when their file has been uploaded successfully?
- Can they check or change what they’ve added before submitting?
- And what does success look like, not just for users, but for the service too?
Shared user needs
Across all our research, some consistent user needs stood out.
Clear guidance from the start
Users want to know up front what file types are allowed, what the size limits are, and how many files they can add. It helps them prepare properly and avoid surprise errors later on.
Support with the mechanics of uploading
Not everyone feels confident with technology. Some need more obvious prompts for choosing files, and reassurance that something is happening once they’ve clicked.
A process that works well in mobile and low-data environments
Many users are on mobile devices, sometimes with limited data or confidence. File upload processes should minimise destructive actions, avoid forcing people to re-upload unnecessarily, and ensure feedback is visible without extra scrolling or searching.
The ability to upload multiple files
Sometimes people need to upload everything at once, while other times they do it bit by bit as files become available. The upload process should support this by being manageable, forgiving, and straightforward.
Visibility and control over what’s been uploaded
People want to see what they’ve added, check that it looks right, remove mistakes, and feel confident before they move on.
Reassurance that files have been received
Users need explicit, visible confirmation both that a file has been uploaded successfully and that it’s part of their submission. Without that clarity, they second-guess and sometimes repeat the task.
Helpful errors, not blockers
A generic “something went wrong” isn’t enough. Users need to know what happened (wrong file type, size, or name), why it happened, and how to fix it, ideally without starting over.
Breaking the task into manageable steps
Some journeys work better when uploads are tackled one at a time, especially if people need to label files, explain their purpose, or don’t have everything ready. A step-by-step approach can help them stay focused and in control.
A better experience for edge cases
Some internal systems support dozens of uploads at once. That raises questions about pagination, sorting, and visibility. We’ve started spotting patterns and opportunities to align.
Clarity around what’s uploaded vs what’s submitted
Uploading a file doesn’t always mean it’s been sent; sometimes it’s just been added to a holding space. That distinction isn’t always clear. Users often assume seeing a file listed means it’s already submitted. The design challenge is how to make that distinction obvious without overloading the interface.
Across government
We’ve been in touch with other teams across government, including HMRC, DEFRA and the Ministry of Justice, and we’ve been following open GitHub discussions. Teams often solve the same problems in slightly different ways, especially around multi-file uploads, drag-and-drop behaviour, and status indicators. There’s a real opportunity here to learn from one another, align where it makes sense, and reduce effort for everyone.
File upload in other design systems
The GOV.UK file upload component is a solid foundation, and DWP teams should use it as the basis for designs. However we want to develop further guidance for how it should work in a wider journey: how we inform users about what's needed, help them choose the right files, support them through the upload, and give them control to manage or change what they’ve added before submission.
We're exploring whether we need:
- more practical, precise guidance for teams
- flexible extensions to the existing GOV.UK component
- a DWP-specific pattern for more complex journeys
If we develop new things we'll do it collaboratively and share what we learn.
Considering the role of AI
Alongside this work, we’re starting to notice places where AI might help with upload journeys mainly in more complex, agent-facing services.
The question for us isn’t whether to add AI, but whether it can actually help people make sense of what they’ve uploaded or avoid unnecessary back-and-forth, without taking judgement away from humans.
This is early thinking, based on a small number of examples, and something we expect to evolve.
Design considerations
Based on what we've learned so far we've identified seven areas where we might be able to establish some rules about good practice for file uploads.
- Set clear expectations early
- Make uploads discoverable and understandable
- Give users control over their uploads
- Provide timely, clear feedback
- Reduce unnecessary barriers
- Design for mobile, edge cases, and real-world use
- Make the upload–submit distinction clear
Could we improve this page?
Send questions, comments or suggestions to the DWP Design System team.
Last updated: