HTML Help Text for File Sizes and Allowed Formats

A form should feel easy to use. The visitor sees a question, gives an answer, and needs to know what will happen next.

What You Need to Know

Visitors see a clear file-type and file-size instruction before picking a file.

Try the Example

Take a look at the example. We’ll explain the important lines right below it.

<form action="/upload" method="post" enctype="multipart/form-data">
    <label for="resume">Upload a PDF resume</label>
    <input id="resume" name="resume" type="file" accept="application/pdf" aria-describedby="resume-help">
    <p id="resume-help">PDF only, up to 5 MB. The server checks both file type and size.</p>
    <button type="submit">Upload</button>
</form>

Let’s Read the Code

<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.
for: For connects a label or output with a control by ID.
id: An id uniquely identifies an element on this page.

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

Rewrite the help text for JPEG photos with a 2 MB limit.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
The accept attribute does not enforce the 5 MB limit; that check belongs on the server.

Key Takeaways

A control needs a clear label and, when submitted, a meaningful name and value.
<form>: The form groups controls and identifies where submitted data goes.
Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.