Text

Free feature

Text is available to all Fomr users.

The Text component allows you to add static text content to your forms. Unlike input components, Text doesn’t collect responses—it displays information, instructions, or context to help guide respondents through your form.

When to use Text

Text works well for:

• Section introductions
• Instructions and guidance
• Legal disclaimers
• Context before questions
• Thank you messages within the form
• Any informational content

Tip

Text components are for display only. They don’t collect any data from respondents.

Adding a Text component

1. Open your form in the editor

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

3. Click the component to select it and edit the content

4. Configure alignment and styling as needed

Configuration options

Content

The text content to display. You can write multiple paragraphs and format your text.

Tips for content:

• Keep text concise and scannable
• Break long content into paragraphs
• Use clear, simple language
• Focus on what respondents need to know

Alignment

Control how the text is aligned:

Alignment	Best For
Left	Body text, instructions (default)
Center	Headings, short messages
Right	Special cases, RTL languages

Variant

Choose a text style variant for visual hierarchy:

Different variants may include:

• Default: Standard body text
• Heading: Larger, bolder text for section titles
• Subtle: Smaller or lighter text for secondary information

Tips for effective use

Keep it brief. Long blocks of text are often skipped. Get to the point quickly.

Use for context, not questions. Text components don’t collect data. Use them to provide information that helps respondents answer actual questions.

Break up long forms. Use text components to introduce sections and give respondents a sense of progress.

Consider visual hierarchy. Use different variants to distinguish between headings, body text, and secondary information.

Don’t overuse. Too many text blocks can make forms feel long. Only add text when it genuinely helps.

Write for scanning. Most people scan rather than read. Use short paragraphs and clear language.

Text vs. description fields

Many components have their own description fields. When to use which:

Use Text Component When	Use Description Field When
Introducing a section	Explaining a specific question
Providing general instructions	Giving format hints
Adding standalone messages	Clarifying what’s being asked
Creating visual breaks	Providing examples

Formatting tips

While the Text component displays plain text, you can:

• Use multiple paragraphs for readability
• Keep sentences short and clear
• Use the variant setting for visual hierarchy
• Combine with Divider components for visual separation

Accessibility

The Text component is built with accessibility in mind:

• Proper text semantics
• Readable by screen readers
• Respects user font size preferences
• Good color contrast

Handling in responses

Since Text components don’t collect data:

• They don’t appear in form responses
• They’re not included in exports
• They’re purely for display purposes