Once a form is active, there are two ways to send people to it.

Getting it there is one click in the dashboard. From the CLI, the API, or an AI agent you have connected, you can ask for it instead — but a form only goes live once a person opens the form's Approve a form publish screen (/forms/<id>/approve), reads the questions it will publish, and enters the approval code the request printed there. A code typed on any other screen approves nothing. See A version isn't the same thing as publishing.

The direct link

Every form has a public address at itsjustbig.com/f/<slug>. A simple single-page form works even without JavaScript — visitors can fill it out and submit on a slow connection or a stripped-down browser. Forms that use multiple pages or conditional logic step through in the browser, so those need JavaScript.

The Client check-in form a coaching practice gets is the exception: its public link works only with the code in a client's update link, so sharing the bare address or a short link to it doesn't let anyone send a check-in. See The client check-in form.

Shorten it

From the form, click Shorten it → to mint a short link in one click. The short link is tied back to the form (form_id), so its clicks and this form's submissions can be looked at together. See Short Links for what a short link is and how its stats work.

Anti-spam

Submissions are rate-limited, and forms carry hidden honeypot fields, a minimum fill time and basic bot filtering to keep automated noise out. This protects your form from casual spam — it isn't a claim of airtight security, and there is no captcha.

The rate limits work at three levels: per visitor's network address, per form, and across your whole workspace. The form and workspace ceilings are high enough that ordinary traffic, even a busy launch, never reaches them; they exist so a single script can't flood a form. A visitor who does hit a limit stays on the form with their answers and a message asking them to try again in a minute.

The thank-you screen means the response was saved. If a submission can't be saved (a temporary error on our side, a limit, or an answer that didn't pass the form's checks), the visitor stays on the form with their answers kept and a message saying what to do. With JavaScript turned off in their browser, they're returned to the form with the same message but have to fill it in again.

Because a stored submission counts against your weekly cap, spam that gets past those filters spends the same budget your automations draw on. A real submission is still never refused — every one is stored, on every plan. But once the cap is spent, the responses that arrive after it are stored locked: you see that they came in, not what they say, until they unlock at the weekly reset. Junk traffic can therefore lock up the genuine leads behind it and, because the released backlog is served before your automations, keep those automations quiet into the following week too. If a public form starts drawing junk traffic, check your usage on Settings → Billing.

Branding

On the free (teeny) plan, public forms show a small "Powered by big" footer. Paid plans don't show it.

There's no embed or iframe support for forms, and no QR code generation — both are unavailable today, share the direct link or the short link instead.