Number

Free feature

Number is available to all Fomr users.

The Number component provides an input field for collecting numeric values. It includes validation options to ensure respondents enter numbers within your specified range.

When to use Number

Number is ideal for collecting:

• Ages
• Quantities or counts
• Prices or budgets
• Years
• Scores or ratings
• Measurements
• Any numeric value

Tip

Use the Number component instead of Short Answer when collecting numeric data. It provides better validation and a numeric keyboard on mobile devices.

Adding a Number component

1. Open your form in the editor

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

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

Configuration options

Question label

The main question or prompt displayed above the input field.

Examples:

• “Age”
• “How many attendees?”
• “Budget (USD)”
• “Years of experience”

Description

Optional helper text that appears below the question label.

When to use descriptions:

• To specify units (years, dollars, etc.)
• To clarify what range is acceptable
• To provide context for the number

Examples:

• “Enter your age in years”
• “Approximate budget in US dollars”
• “Number of team members including yourself”

Placeholder

Ghost text that appears inside the input field when it’s empty.

Examples:

• “25”
• “Enter amount”
• “0”

Minimum value

Set the lowest acceptable number. Entries below this value will show a validation error.

Use cases:

• Age fields (minimum 0 or 18)
• Quantity fields (minimum 1)
• Year fields (minimum 1900)

Maximum value

Set the highest acceptable number. Entries above this value will show a validation error.

Use cases:

• Age fields (maximum 120)
• Rating scales (maximum 10)
• Percentage fields (maximum 100)

Required

Toggle whether this field must be filled out before the form can be submitted.

When enabled:

• An asterisk (*) appears next to the question label
• Users cannot submit without providing a valid number
• Validation errors appear for empty or out-of-range entries

Validation

The Number component validates entries to ensure:

• The input is a valid number
• The number is within the min/max range (if set)
• The field isn’t empty (if required)

Validation messages:

• “This field is required” - when empty and required
• “Value must be at least [min]” - when below minimum
• “Value must be at most [max]” - when above maximum

Tips for effective use

Set appropriate min/max values. Use validation to prevent obviously incorrect entries (like negative ages or quantities over 1000).

Specify units clearly. If the number represents a specific unit (dollars, years, people), make that clear in the label or description.

Use sensible defaults. Consider what the most common answer might be and use that as a placeholder hint.

Consider alternatives for ranges. If you only need approximate values, consider using a Slider or Linear Scale instead.

Don’t over-restrict. Set min/max values that make sense, but don’t be so restrictive that legitimate responses are rejected.

Mobile optimization

The Number component is optimized for mobile devices:

• Triggers the numeric keyboard on mobile devices
• Shows number keys for faster entry
• Supports decimal input where appropriate

Decimal numbers

The Number component accepts decimal values (e.g., 3.5, 10.99). If you only want whole numbers, mention this in your description.

Accessibility

The Number component is built with accessibility in mind:

• Input type is set to “number” for proper semantics
• Labels are properly associated with input fields
• Validation errors are announced to screen readers
• Keyboard navigation is fully supported
• Increment/decrement controls are accessible