The Field Settings tab allows you to customize how each individual field behaves and appears.

While the Structure tab controls field order, and Form Settings controls global behavior, Field Settings is where you fine-tune each field.

This guide explains every configurable option available for both Basic and Advanced Fields.

How to Access Field Settings

1. Open your form in the Form Builder.
2. Go to the Structure tab.
3. Click any field.
4. Switch to the Field Settings tab.

You will now see the configuration options for that specific field.

Always click Save Form after making changes.

Field Label

The visible name displayed above the field.

Example:

• Full Name
• Email Address
• Message

Why It Matters

The label tells users what information to enter.

It is also used in:

• Email notifications
• Submission records
• CSV exports

Best Practices

✔ Keep labels clear and concise
✔ Avoid vague names like “Info”
✔ Use consistent naming across fields

Placeholder Text

Light hint text displayed inside the field.

Example:

• Enter your full name
• example@email.com

Placeholders disappear when the user starts typing.

When to Use It

Use placeholders to:

• Provide formatting hints
• Give example input
• Reduce confusion

Avoid using placeholders as the only instruction — always use a proper label.

Required Field

Makes the field mandatory before submission.

When enabled:

• Users must fill out the field.
• The form cannot be submitted without it.

When to Use Required

Use Required for:

• Email address
• Name
• Essential contact information

Avoid requiring unnecessary fields — this improves completion rates.

Default Value

Pre-fills the field with a preset value.

Example:

• Country set to “United States”
• Budget field pre-filled with “1000”

When to Use Default Values

• Setting common options
• Pre-filling internal fields
• Saving user time

Be cautious — default values can influence user responses.

Column Width

Controls how much horizontal space the field occupies.

Common options:

• 100% (Full Width)
• 50%
• 33%
• Custom percentage (if supported)

Examples

• 50% + 50% → Two fields on one row
• 33% + 33% + 33% → Three fields on one row

Best Practices

✔ Keep long fields (Textarea, Address) full width
✔ Use 50% for First/Last name
✔ Avoid overcrowding rows

For detailed layout examples, see:
Creating Multi-Column Layouts

Conditional Logic

Shows or hides fields based on user input.

When enabled, you can define rules such as:

If “Business” is selected → Show “Company Name”

How It Works

You define:

• A trigger field
• A condition (equals, not equals, etc.)
• An action (show or hide)

Best Practices

✔ Keep logic simple
✔ Test every scenario
✔ Avoid conflicting rules

For full details, see:
Using Conditional Logic

Field Options (Dropdown, Radio, Checkbox Group)

For selectable fields, you can define custom options.

Example for Dropdown:

• Sales
• Support
• General Inquiry

Tips

✔ Keep option text clear
✔ Avoid too many options
✔ Use Dropdown for long lists
✔ Use Radio for short visible lists

Min / Max Values (Number & Date Fields)

Some fields support minimum and maximum values.

Example:

• Minimum age: 18
• Maximum quantity: 10

When to Use It

• Limiting bookings
• Enforcing eligibility rules
• Preventing unrealistic input

File Upload Settings (Advanced Field)

For File Upload fields, additional settings may include:

• Allowed file types
• Maximum file size
• Number of files allowed

Best Practices

✔ Restrict file types (e.g., PDF, JPG)
✔ Keep file sizes reasonable
✔ Test uploads before publishing

Hidden Field Configuration

Hidden fields allow you to store internal data.

You can:

• Set a fixed value
• Track campaign source
• Pass internal identifiers

Users cannot see or edit hidden fields.

HTML Block Settings

HTML Blocks allow you to insert formatted content into your form.

You can use them for:

• Section titles
• Instructions
• Disclaimers
• Custom layout content

They do not collect data.

Field-Level Styling (If Available)

Depending on your setup, some fields may allow:

• Custom CSS classes
• Special formatting
• Alignment control

Use carefully to maintain consistent design.

Field Settings and Email Notifications

Field labels appear in:

• Email subject (if used as placeholders)
• Email message body
• Submissions list
• CSV export

Changing a label changes how it appears in emails.

Always double-check your email template after renaming fields.

Field Settings and Submissions

Each field configuration affects how data is stored.

For example:

• Required ensures complete submissions
• Default values influence stored data
• Hidden fields add metadata

Review your settings carefully before publishing.

Recommended Workflow

For each new field:

1. Add the field.
2. Set the label.
3. Add placeholder (if helpful).
4. Decide if it should be required.
5. Adjust column width.
6. Add conditional logic (if needed).
7. Save the form.

Repeat for each field.

Common Mistakes

Too Many Required Fields

This reduces submission rates.

Overusing Conditional Logic

Complex logic can confuse users.

Poor Labeling

Unclear labels cause incorrect submissions.

Ignoring Mobile Layout

Always preview column widths for mobile stacking.

Best Practices for Professional Forms

✔ Keep forms focused
✔ Group related fields
✔ Use Section Breaks for clarity
✔ Combine layout + logic wisely
✔ Test before publishing

Related Guides

To maximize your form setup, explore:

• Basic Fields – Complete Guide
• Advanced Fields – Complete Guide
• Creating Multi-Column Layouts
• Using Conditional Logic
• Email Notifications Setup