LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • 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
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Allowing images taken by a camera
  • Setting up a bucket
  • Creating a filename pattern
  • Specifying file types allowed
  • Allowing multiple answers
  • Restricting image upload size

Was this helpful?

  1. Building flows
  2. Adding content
  3. Questions

Image upload

An image uploaded from the user, optionally via the camera

PreviousIframeNextNumber

Last updated 2 months ago

Was this helpful?

This question type is used in cases where you would like the user to take a picture of a document, ID card or themselves.

If you would like the responder to be able to upload files as opposed to take images, you can use the content type. If you would like the responder to sign a document, you can use the content type.

If you don't want the responder to be held up by an image upload question, make sure to have the question be .

Allowing images taken by a camera

By enabling Allow camera option in the settings menu with the question selected, you can give the responder the option to upload their image by taking a photo on their supported devices. The default camera on mobile devices is the front camera and you can mirror the image taken (depending on whether you expect your subjects to be people or documents) by enabling the Mirror image? option.

Setting up a bucket

In order to have the responder upload an image, you need to set up a or to specify where the file will be stored. For detailed instructions on setting up a file integration in Formsort, you can go to thisand this page for

Creating a filename pattern

You can opt to define a naming pattern for the images that your responders upload by enabling Filename pattern in the question settings.

You can any relevant variable you would like to be included in the name of the file into the field. For example, if you type in {{first_name}} into the field, the value of the first_name variable will be used as the filename at upload.

Formsort offers three custom variables for these types of file upload components, built right into the settings of the component itself: sessionUuid, randomUuid, and currentTimeUTC. These variables can also be templated into the filename pattern field to create dynamic filenames.

  • sessionUuid: a uuid that is created once, when the form is loaded.

  • randomUuid: a uuid that is created at and re-run at each upload instance.

  • currentTimeUTC: a timestamp that is created at and re-run at each upload instance.

You can use several of these variables at once, if required, and one pattern we suggest is {{currentTimeUTC}}_{{responder_uuid}}. This ensures uniqueness via the timestamp, while still tying the file to a particular user via the responder_uuid System Library variable.

Note that these extensions will be added automatically. You should also set a fallback naming convention in case the variable is not defined by typing it into the Filename pattern fallback field. Values here cannot use templated variables.

Specifying file types allowed

You should whitelist MIME types when generating signed upload URLs.

Allowing multiple answers

Restricting image upload size

You can enable a size restriction for a responder's upload. The minimum value must be greater than 0. If the restriction is not met, the responder will be shown an error and be prevented from moving forward in the flow.

Visit the section for details on built-in variables that provide information about the responder's environment and context.

You can whitelist by adding them to the Allowed MIME types field. If none are set, all MIME types will be allowed.

Enabling lets the respondent upload more than one image as an answer to a question.

๐Ÿ—๏ธ
System Library variables
MIME (Multipurpose Internet Mail Extension) types
file
signature
S3 bucket
GCS bucket
page for s3
GCS.
template
allow multiple uploads
optional