Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
The file picker suggests PNG and JPEG choices based on MIME-type hints.
In this example: offer PNG and JPEG file selection.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/files" method="post" enctype="multipart/form-data">
<label for="photo">Upload a photo</label>
<input id="photo" type="file" name="photo" accept="image/png,image/jpeg">
<button type="submit">Upload</button>
</form>Let’s Read the Code
- accept: Accept suggests which files should be selectable; it is not file security validation.
- type: Type changes what sort of control or resource the browser uses.
- <form>: The form groups controls and identifies where submitted data goes.
- <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.
What Happens in the Browser?
The HTML controls work in the browser, but saving an answer requires the example action path to be handled by a real server.
What happens to the file? Choosing a file does not upload it immediately. The browser sends it when the form is submitted to an endpoint that accepts file uploads. The server must check the file type, size, and permissions before storing it.
Your Turn
Change the accept list to application/pdf and explain what should happen in the picker.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- You cannot trust accept to protect the upload endpoint. Validate content and size on the server.
Key Takeaways
- Choose the HTML feature that explains this task clearly.
- accept: Accept suggests which files should be selectable; it is not file security validation.
- Test the behavior you expect rather than trusting how the snippet looks in your editor.