Once a form is built, there are three ways to put it in front of people: its own link, a snippet that embeds it in your website, or a post from a form in your own page. You also choose whether anyone can open it, who it takes responses from, whether visitors agree to your privacy policy, and what they see afterwards.
The form needs to be Live to take responses. See Build a form.
You need to be able to change the form to edit its settings. Anyone on the form can open Share and copy its link. See Who can see a form.
Open the form and choose Share.
On the Link tab, copy the Form link and send it to people.
The link opens the form on a page of its own, in your organisation's branding.
Open the form's Settings tab.
Under Who can open it, choose:
Public: the form opens for anyone with its address.
Secret link: the link also carries a key, so the form can't be found by guessing.
Choose Save settings.
A secret form's link, embed code and posting address all include its key. Copy them again from Share after you switch.
If a secret link has travelled further than you'd like, replace its key.
Open the form and choose Share.
Choose Replace the key, then Replace key.
Every link and embed that carries the old key stops working straight away, so share the new ones.
Open the form and choose Share.
On the Embed tab, copy the Embed code.
Paste it into your page where the form should appear.
The form takes the width of its container and grows to fit as a visitor moves through it, on any screen size.
If you'd rather keep your own form's design, your page can post its answers straight to 53°.
Open the form and choose Share.
Open the Your own form tab and turn on Take posts from my own website. It takes effect straight away.
Copy the Post to address, or the Starting markup, which has an input for each of your fields.
Name each input after its field's Key. You'll find the key at the bottom of each field on the Build tab.
What to know about posting this way:
It's off until you turn it on, because these posts can't carry our bot check. Leave it off unless you need it, and protect your own form.
Files can't be sent this way. A File upload field is left out of the starting markup.
Keep the last input in the starting markup, the one named fax_number. It's moved off the screen so people never see it, and it's there to catch scripts: a post with anything in it is dropped.
For a field with options, send the option's label.
After posting, the visitor goes to your own page if you've set one under After sending. Otherwise they see a plain page saying their response has been sent.
For a full example, what to send for each field type, and the checks we recommend you add, see Post to a form from your own website. Learn more on the Your own form tab opens the same article.
You can take responses only from certain email addresses or domains. The form checks the address entered in one of its email fields, so it needs an Email field first.
Open the form's Settings tab.
Under Who can send, turn on Only take responses from certain senders.
Choose the Email field to check.
Under Allowed addresses and domains, enter whole addresses, or domains such as @example.com. Separate them with commas or put each on its own line.
Choose Save settings.
You can list up to 100 addresses and domains.
A new form asks visitors to agree to your organisation's privacy policy before they send.
Open the form's Settings tab.
Under Privacy policy, turn Ask visitors to agree to our privacy policy on or off.
Choose Save settings.
While it's on, the form's own page and its embed show a switch, "I agree to the privacy policy", with a link to your policy. The form won't send until the visitor turns it on. In the inbox, the response's header then says "Agreed to your privacy policy".
The link comes from your organisation's brand settings. If no privacy policy link has been added there, forms don't show the switch, and the Settings tab says so. Owners and admins see a Brand settings button beside that note, which goes straight there.
On the Settings tab, under After sending:
Button label is the text on the form's send button. It starts as "Send".
Message is what the visitor sees once their response has gone. It starts as "Thanks. Your response has been sent."
Or send them to a page of your own takes a full link, which has to start with https://. On the form's own page, the visitor is taken straight there. In an embed, they see your message with a Continue button that leads there.
Choose Save settings when you're done.
The form's own page and the embed run a bot check, provided by Cloudflare Turnstile, before a response is taken.
The privacy policy switch isn't shown for posts from your own website. If you need agreement there, add it to your own form.
Forwarding responses by email, and assigning them by an answer, are steps in the form's automation. See Automate a form.
If you open Share on a form that isn't live, a note tells you. A draft's link shows "This form isn't available" to visitors. A closed form's link shows that it has stopped taking responses.
If a lot of responses arrive from one place in a short time, the visitor is asked to wait a few minutes and try again.
A form's link stops working while your organisation has no plan.
Each response counts towards your plan's monthly allowance, however it arrives. See Plans and billing.
