<input type="hidden">

<input> elements of type "hidden" are used to allow web developers submit data along with forms that cannot be seen or modified by users, for example the ID of the content that is currently being ordered or edited, or a unique security token. Hidden inputs are completely invisible in the rendered page, and cannot be made visible in any way.

Note: There is a live example below the following line of code — if it is working correctly, you should see nothing!

<input id="prodId" name="prodId" type="hidden" value="xm234jq">

Value A DOMString representing the value of the hidden data you want to pass back to the server.
Events None.
Supported Common Attributes autocomplete
IDL attributes value
Methods None.


The <input> element's value attribute's value contains a DOMString that contains the value of hidden data you want to pass to the server. This specifically can't be edited by the user via the user interface, although you could edit the value via browser developer tools.

Using hidden inputs

As mentioned above, hidden inputs can be used anywhere that you want to submit data to the server along with a form secretly — without the user knowing about it or being able to edit that data. Let's look at some examples that illustrate its use.

Tracking edited content

One of the most common uses for hidden inputs is to keep track of what database record needs to be updated when an edit form is submitted. A typical workflow looks like this:

  1. User decides to edit some content they have control over, such as a blog post, or a product entry. They get started by pressing the edit button.
  2. The content to be edited is taken from the database and loaded into an HTML form to allow the user to make changes.
  3. After editing, the user submits the form, and the updated data is sent back to the server to be updated in the database.

The idea here is that during step 2, the ID of the record being updated is inserted into a hidden input. When the form is submitted in step 3, the ID is sent back to the server with the record content. The ID lets the site's server-side component know exactly which record needs to be updated with the submitted data.

You can see a full example of what this might look like in the Examples section at the bottom of the article

Improving webite security

Hidden inputs are also used to store and submit security tokens or secrets, for the purposes of improving website security. The basic idea is that if a user is filling in a sensitive form, such as a form on their banking website to transfer some money to another account, the secret they would be provided with would prove that they are who they say they are, and that they are using the correct form to submit the transfer request.

This would stop a malicious user from creating a fake form, pretending to be a bank, and emailing the form to unsuspecting users to trick them into transferring money to the wrong place. This kind of attack is called a Cross Site Request Forgery (CSRF); pretty much any reputable server-side framework uses hidden secrets to prevent such attacks.


Hidden inputs don't participate in constraint validation; they have no real value to be constrained.


Let's look at how we might implement a simple version of the edit form we described earlier (see Tracking edited content).

The edit form might look a little bit like this:

    <label for="title">Post title:</label>
    <input type="text" id="title" name="title" value="My excellent blog post">
    <label for="content">Post content:</label>
    <textarea id="content" name="content">
This is the content of my excellent blog post. I hope you enjoy it!
    <button type="submit">Update post</button>
  <input type="hidden" id="postId" name="postId" value="34657">

Let's also add some simple CSS:

html {
  font-family: sans-serif;

form {
  width: 500px;

div {
  display: flex;
  margin-bottom: 10px;

label {
  flex: 2;
  line-height: 2;
  text-align: right;
  padding-right: 20px;

input, textarea {
  flex: 7;
  font-family: sans-serif;
  font-size: 1.1rem;
  padding: 5px;

textarea {
  height: 60px;

The output looks like this:

Note: You can also find the example on GitHub (see the source code, and also see it running live).

When submitted, the form data sent to the server will look something like this:


Even though the hidden input cannot be seen at all, its data is still submitted.


Specification Status Comment
WHATWG HTML Living Standard
The definition of '<input type="hidden">' in that specification.
Living Standard Initial definition
HTML 5.1
The definition of '<input type="hidden">' in that specification.
Recommendation Initial definition

Browser compatibility

Feature Chrome Edge Firefox (Gecko) Internet Explorer Opera Safari
Basic support 1.0 (Yes) 1.0 (1.7 or earlier) (Yes) 1.0 1.0
Feature Android Chrome for Android Edge Firefox Mobile (Gecko) IE Mobile Opera Mobile iOS WebKit
Basic support (Yes) (Yes) (Yes) 4.0 (2.0) (Yes) (Yes) (Yes)

See also

Document Tags and Contributors

 Contributors to this page: chrisdavidmills
 Last updated by: chrisdavidmills,