A form is a public page at /f/:slug that collects structured responses from anyone with the link. No Instagram connection, no code.

What a form is

Each form lives at its own itsjustbig.com/f/<slug> address. Visitors fill it out and submit — you see the responses in your dashboard. That's the whole loop.

Create a form

1. Open Forms in big and click New form.
2. Give it a title.
3. Add your fields — see Field types for what's available.
4. Set status to active when you're ready to accept submissions.

Already have a form in Typeform? You can import it instead of rebuilding it — open Forms → Import, connect your Typeform account, and pick a form to bring over.

Form settings

• Title — shown at the top of the public form.
• Status — draft, active, or closed. Only active forms accept submissions; draft and closed forms still exist and can be viewed in your dashboard, but visitors can't submit to them.
• Slug — auto-generated from the title when you create the form. There's no way to change it afterward, so don't rely on the slug spelling out something you might want to edit later.

Pages and logic

A form isn't limited to a single screen. You can split it into multiple pages (up to 20) and add conditional logic:

• Show a field only when it's relevant — a field can be set to appear based on an earlier answer.
• Branch between pages — at the end of a page, send the respondent to a different page (or straight to submit) depending on what they answered.

This lets one form ask follow-up questions that only apply to some people. You build it visually in the form editor — there's nothing to write. Conditional logic covers the rules in detail.

The confirmation screen

You can customize what a respondent sees after they submit:

• A custom heading and message (your own thank-you text).
• An optional button with your own label, linking to any URL you choose.

Leave these blank and big shows a standard thank-you.

What's not there yet

To set expectations up front, a form today does not support:

• A description field on the public page (only a title and per-page headings)
• An automatic redirect to another URL after submit (you can add a button the visitor taps, but the page doesn't redirect on its own)
• Logo, color, or other branding configuration

If you need any of these, they're not available yet — don't build a workflow that depends on them.

Fields

Forms support 10 field types, each with its own validation. See Field types for the full list.

Share it

Once a form is active, share the public link or turn it into a trackable short link. See Share your form.

Limits

• 1–100 fields per form, across 1–20 pages.
• Each field needs a unique field ID.
• Submitted answers are capped at 16KB total per submission.
• There's no plan-based cap on the number of forms or fields — every plan gets the same limits above.
• Submissions count against your plan's weekly cap, which they share with automation steps. Views don't count; only a stored submission does.
• A submission is never refused. Going over the cap never costs you a response: every submission is accepted and stored, on every plan, at any usage level. The visitor sees the same thank-you screen either way.
• Over the cap, a response is stored locked. You still see that it arrived, when it arrived, and it still counts in your totals and conversion rate. You don't see the answers, who submitted it, or which link or campaign it came from, until it unlocks.
• Locked responses unlock at the weekly reset, oldest first, as far as the new week's budget stretches. Upgrading unlocks all of them immediately.
• The unlocked backlog is served before your automations. Releasing locked responses draws on the new week's budget first, so DM and comment automations only start firing again once the backlog has been cleared. A backlog bigger than your weekly cap drains over several weeks, and your automations stay quiet the whole time. See Plans.