LogoLogo
Back to studio
  • 🧠Core Concepts
    • Introduction to Formsort
    • Formsort quickstart guides
      • Add content and collect answers
      • Capture demographic data
      • Add informational content
      • Template your variables
      • Add conditional logic
      • Using conditional logic with Calculated and API variables
      • Add a scheduling option
      • End the flow
      • Review your variable schema
      • Set up integrations
    • How data works in Formsort
      • Responder UUIDs
    • Understanding flows
    • Versioning in Formsort (Deploying)
      • Variant revisions
      • Managing revisions
  • ✨Creating Flows
    • Building a new flow
      • Groups
      • Steps
      • Copy-pasting form content
  • Adding questions and content
    • Questions
      • Select
      • Text
      • Address
      • Comparison
      • Confirmation
      • Date
      • Date & time
      • Email address
      • File upload
      • Grid choice
      • Iframe
      • Image upload
      • Number
      • Payment
      • Phone number
      • Postal code
      • Question group
      • Region
      • Signature
      • SSN
      • Yes/No
    • Content
      • Statement
      • Image
      • Next button
      • Video
      • Divider
      • Map
  • Controlling the flow with conditions and logic
    • Advanced logic
  • Variable templating
  • Redirects and endings
  • Field validation
  • Flow and variant management
  • Content library
  • 🧬JSON Form Definition
  • JSON schemas
  • Validating flow schemas
  • Events subscriptions
  • Flow content data format
  • 🎨Styling
    • Customizing appearance
      • Content area & form layout
      • Buttons
      • Typography
      • UI states
      • Color and dimension variables
      • Question containers
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
      • Animations and transitions
  • CSS & Advanced Styling
    • Custom CSS overrides
    • Step styling
    • CSS reference
  • 🔁Form Behavior Settings
    • Variant settings
      • Form behavior for returning users
      • Group ranking API
    • Navigation sidebar
  • ⚙️Response Data Collection & Management
    • Schema (variables)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
  • Saving & retrieving responses
  • Importing Data
    • URL parameters
    • POST body
    • Embed query parameters
  • 📊Analytics and Attribution
    • Built-in analytics
    • Split testing
  • 🚀Publishing and Deployment
    • Live preview overview
    • Environments
      • Loading different environments
    • Embedding
      • Web-embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Pre-deployment checklist
  • 📁Workspace Management
    • Accounts
      • Roles and permissions
    • Custom domains
    • Workspace domain detection
  • 🛠️Formsort Admin API
    • Admin API
  • 🔌Integrations
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
Powered by GitBook
On this page
  • Select buttons
  • Next button
  • Skip button
  • Previous button
  • Exit button
  • Restart button
  • Default buttons

Was this helpful?

  1. Styling
  2. Customizing appearance

Buttons

CTA all day.

PreviousContent area & form layoutNextTypography

Last updated 1 day ago

Was this helpful?

Buttons are very useful, and have many different applications in Formsort. Below are the some options provided, as well as some insight on configuring their behavior and design.


Select buttons

Select questions (and Boolean questions) can use customizable Select buttons to display choices to the responder. There are three main styles available—Default, Checkmark, and Image—each with its own configuration options.

Like other design elements in Formsort, Select buttons can be styled on a per-UI basis.

Select Button Types

Default

The Default style presents a clean button with just a label—no icons or imagery. This is the base styling applied unless other visual features are enabled.

Checkmarks

When Show checkmarks and radio buttons on choices is enabled in the Style tab of a Select question, checkmarks (or radio buttons) appear inside the choice buttons.

Styling for checkmark-based buttons is controlled in two places:

  • Theme → Buttons → Select → Checkmark → Controls button styling, and checkmark positioning.

  • Theme → Checkmarks → Controls the styling of the checkmark or radio icons.

    • Checkmark styles will adapt styles defined in either Single choice or Multiple choice based on whether Allow multiple selection is enabled or not.

You can also control the vertical alignment of the checkmarks from the right-hand menu.

Image

Enabling Show images on choices in the Style tab allows you to add images, videos, or GIFs to select choices.

After enabling this option, you can add media directly within each choice configuration.

Image-style settings are located under:

Theme → Buttons → Select → Image

Layout Options

You can adjust how choices are laid out within a Select question. Available layout styles include:

  • Grid

  • Vertical (default)

  • Horizontal

  • Snug

  • Space Around

  • Space Between

The layout setting can be adjusted directly on the Select question.

Style Overrides

Because Select buttons are used in various design contexts, you can override default styling on a per-question basis.

To do this:

  1. Select the question.

  2. Open the Style tab.

  3. Enable Override default select button style.


Next button

The Next button position can be configured in Layout, and style settings can be found in the Buttons → Next section of the Theme tab.

Style options

By default, the Next button will only appear when the user has answered all the required questions and needs a way to move forward. You can opt to "Always show next button" by enabling the setting under Behavior, in which case the Next button will show in it's Disabled state until the user is available to proceed.

By default, "Next" is provided as the button label, but this can be modified or removed by changing the string inside the Label input.

You can add an Image to your next button, style settings for which can be found at the bottom of the menu under Image style once an image has been added.

Next button style override


Skip button

Options

By default, the button will have "Skip" as the copy inside the button, but this can be modified or removed by changing the string inside the Label input.

You can add an Image to your skip button, style settings for which can be found at the bottom of the menu under Image style once an image has been added.


Previous button

The previous button is optional, but recommended - it gives responders more control in navigating the flow.

Options

By default, the button will have "Previous" as the copy inside the button, but this can be modified or removed by changing the string inside the Label input.

You can add an Image to your Previous button, style settings for which can be found at the bottom of the menu under Image style once an image has been added.


Exit button

If you enable the exit button in the style editor, users will be able to click it to abandon the flow.

There are a few cases where having a close or exit button is helpful:

  • If users are accessing your flow directly, but you wish to bring them to your own page if they are abandoning.

    • If you set a redirect URL then they will be brought to that URL.

    • The parent window will receive the FlowClosed event when this happens, so you can close the Formsort embed in your code.

Options

By default, the button will have an "X" as the copy inside the button, but this can be modified or removed by changing the string inside the Label input.

You can add an Image to your Exit button, style settings for which can be found at the bottom of the menu under Image style once an image has been added.


Restart button

If you add a restart button to your flow, the user will be able restart the flow with all their inputs cleared.

By default, the Restart button will have "Restart" as the copy inside the button, but this can be modified or removed by changing the string inside the Label input.

You can add an Image to your Restart button, style settings for which can be found at the bottom of the menu under Image style once an image has been added.


Default buttons

The default button styles will be applied to any buttons not listed above.

For more details, see our documentation on .

The button is probably the most important button within the flow. Clicking it will advance the user to the next available step.

If you've added your on a step, the style settings can be overriden in the component's style menu. With the component selected, open the Style menu and disable "Use default select button style".

A skip button will appear if enabled, but only on steps where all questions within the step are . Of course, the responder could just click the Next button in this case, but having an explicit skip action may help people understand that their responses are not required on the current step.

If Formsort and you need a way to allow users to close without abandoning the page entirely.

🎨
Styling checkmarks and radio buttons
Next
Next button as a component
embedding
optional