Checkbox

Free feature

Checkbox is available to all Fomr users.

The Checkbox component provides a single checkbox for collecting yes/no or true/false responses. Use it for confirmations, agreements, and binary choices where respondents need to explicitly opt in or acknowledge something.

When to use Checkbox

Checkbox is ideal for:

• Terms and conditions acceptance
• Privacy policy agreements
• Newsletter opt-ins
• Confirmation of understanding
• Single yes/no questions
• Consent collection

Tip

For multiple options where users can select several items, use the Checkboxes component instead. For a more visual toggle, consider the Switch component.

Adding a Checkbox component

1. Open your form in the editor

2. Drag the Checkbox component from the left sidebar onto your form

3. Click the component to select it and configure its settings

Configuration options

Question label

The text that appears next to the checkbox. This should clearly describe what the user is agreeing to or confirming.

Tips for effective labels:

• Be clear and specific about what checking the box means
• Use action-oriented language
• Keep it concise but complete

Examples:

• “I agree to the Terms of Service and Privacy Policy”
• “Subscribe to our newsletter”
• “I confirm that the information provided is accurate”
• “Yes, I would like to receive updates”

Description

Optional helper text that appears below the checkbox. Use this for additional context, or to add links to relevant documents using the description’s formatting tools.

When to use descriptions:

• To link to terms or policies
• To explain what happens when checked/unchecked
• To add legal disclaimers

Examples:

• “Read our Terms of Service and Privacy Policy” (with each linked)
• “You can unsubscribe at any time”
• “Required for participation in the program”

Required

Toggle whether this checkbox must be checked before the form can be submitted.

When enabled:

• Users must check the box to submit the form
• A validation message appears if they try to submit without checking
• Commonly used for terms acceptance and required confirmations

Note

Making a checkbox required means users MUST check it. This is appropriate for mandatory agreements but not for optional preferences.

Tips

• Be specific about what users are agreeing to — Vague checkbox labels can lead to confusion or legal issues.
• Link to relevant documents — If referencing terms or policies, provide links in the description so users can review them.
• Only require when necessary — Required checkboxes should be reserved for genuinely mandatory agreements, not preferences.
• Use positive language — Frame checkboxes as opt-ins (“Yes, I want…”) rather than opt-outs (“No, don’t…”).
• Keep labels readable — Long legal text can be overwhelming. Summarize in the label and link to full documents.
• Consider placement — Place agreement checkboxes near the submit button where users expect to confirm before submitting.

Checkbox states

The checkbox has two states:

State	Meaning
Unchecked	User has not agreed/confirmed (default)
Checked	User has agreed/confirmed

Validation

When a checkbox is marked as required:

• The form cannot be submitted until the box is checked
• A validation message appears if submission is attempted without checking
• The checkbox is highlighted to draw attention

Accessibility

The Checkbox component is built with accessibility in mind:

• Proper checkbox input semantics
• Labels are clickable (clicking the label toggles the checkbox)
• Keyboard accessible (Space to toggle)
• Screen reader compatible
• Focus states are clearly visible

Handling responses

Checkbox responses in your form results:

• Display as “Yes” or “No” (or checked/unchecked)
• Can be filtered to see who agreed vs. didn’t
• Are included in exports as boolean values
• Useful for segmenting respondents

Legal considerations

When using checkboxes for legal agreements:

• Ensure the checkbox label clearly states what users are agreeing to
• Provide easy access to the full terms being agreed to
• Keep records of when and how consent was given
• Consider jurisdiction-specific requirements (GDPR, CCPA, etc.)

Caution

This documentation provides general guidance. Consult with legal professionals for specific compliance requirements in your jurisdiction.