Hidden

Use Hidden when the form needs to carry a value without showing it to the person filling out the form.

Hidden fields are useful for context, attribution, and routing data. Do not rely on them for security-sensitive decisions because hidden values can still be changed before submission.

Key settings

• Default value - Set the value submitted with the form.
• Value source - Populate from a preset, Custom Value, Template, query string parameter, or cookie where supported.
• Custom Value - Literal text with optional variable-picker tokens ({field:handle}, {form:handle}, and so on). If the visitor submits a non-empty value, that posted value is stored.
• Template - A Craft object template (opens new window) resolved only on the server. Posted values are ignored. Use this for trusted computed values such as event context, custom currentUser fields, or query parameters via {request.param.myParam}.
• Prefill query parameter - Read a value from a specific query string parameter.
• Handle - Choose a stable field handle for integrations, templates and exports.

Custom Value vs Template

Use Template when the hidden value must not be tampered with (for example event cost, entitlement flags, or routing metadata). Use Custom Value for tracking tokens or values that may legitimately vary per submission.

Extend template context in PHP with HiddenDefaultTemplateResolver::EVENT_DEFINE_CONTEXT when you need entry lookups or other project-specific variables.

Submitted value

Hidden stores a submitted value like other fields, even though the user does not see a visible control. For Custom Value and preset sources, treat the stored value as user-modifiable browser data unless you validate it server-side. Template defaults are re-resolved on the server and ignore posted input.

When querying or saving submissions through GraphQL, the field handle is used as the field name. Query the form’s formFields and include inputTypeName if you need to confirm the generated input type for a specific form.

Theme config

The Hidden field can be targeted with the hiddenField theme config key.

{{ craft.formie.renderForm('contactForm', {
    themeConfig: {
        hiddenField: {
            field: {
                attributes: {
                    data: {
                        tracking: 'campaign',
                    },
                },
            },
        },
    },
}) }}

Hidden fields usually need little presentation customization. Use a template override only when the hidden input output itself needs to change.

For full Tailwind, Bootstrap and other framework examples, see Formie theme configs (opens new window).

Front-end reference

Hidden fields are still rendered into the page HTML. Do not place secrets, trusted prices, permission flags or other security-sensitive values in a hidden field without server-side validation.

The front-end docs live on the separate browser UI reference site and cover rendered markup, data attributes, styling classes and JavaScript behavior for custom front-end implementations.

• Hidden

Related fields

• Use Single-Line Text when the user should see and edit the value.