A webpage is not always broken because of a large mistake. Small details can produce exactly this problem: debugging: file upload is empty. This guide shows you what to look for, a concrete fix, and how to check that it worked.
The Idea in Plain English
A file input needs a name and form enctype="multipart/form-data" when submitting its file bytes.
You can test this using a small local HTML file. Change one part at a time and check the result in the browser before adding more code.
A Working Example
The first part shows a problem. The second part shows a safer or more accurate version. Compare them before reading the explanation.
<!-- Problem -->
<form action="/upload" method="post">
<input type="file" name="photo">
</form>
<!-- Corrected example -->
<form action="/upload" method="post" enctype="multipart/form-data">
<label for="photo">Photo</label>
<input id="photo" type="file" name="photo">
<button type="submit">Upload</button>
</form>What Each Part Does
- The form collects and submits named fields to the destination specified by action.
- The input creates a field; its type changes the editing controls and the name identifies submitted data.
- The label tells visitors and assistive tools what a control is for.
- action sets the URL that receives a submitted form.
- method chooses GET or POST for form submission.
- type chooses the relevant kind of script, input, media or embedded object.
Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
Try It Yourself
Select a file and inspect the multipart request. The server must still enforce size/type limits.
Common Beginner Mistakes
- Check the underlying cause before changing unrelated tags.
- Changing several parts of the example at once, making it difficult to see which part caused a different result.
- Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.
Key Takeaways
- A file input needs a name and form enctype="multipart/form-data" when submitting its file bytes.
- Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.