Is a public form key a security risk?
No. Anyone can see it, and it only identifies your form.
A form key identifies which form a submission belongs to, and it sits in your page's HTML so the browser can send it. It can only send a submission to your form. It cannot read your submissions or account data, and it cannot change settings, so exposing it does not expose your data.
Why the key is public
A static site has no server of its own to hide a secret on. The browser posts the form straight to Static Forms, so the key has to travel with the request, and anyone can see it with View Source. This is the same as a Stripe publishable key or a reCAPTCHA site key: it names the form and grants no access to your data.
| Form key (public) | API secret key (private) | |
|---|---|---|
| Where it lives | Your page HTML | Your server only |
| What it can do | Send a submission to one form | Read or change data, often for a whole account |
| If it is seen | Visitors can post to that form, within your limits | Someone can act as you |
| Fix if abused | Rotate the key | Rotate the key and audit what it touched |
Why a scanner may flag it anyway
Secret scanners and some security audits match the shape of a key in source code and report it as a hardcoded credential (CWE-798). They cannot tell a public identifier from a secret. The finding is a false positive for a form key. Your CAPTCHA secret keys are different: you enter them in Static Forms, and they never belong in your HTML.
What protects the form
Since anyone can see the key, the protections below limit who can send and how much.
- Domain restriction (Starter and above). Static Forms checks the
OriginorRefererheader against your approved domains and rejects other origins with a 403, and also rejects a request that has neither header. The Allow localhost option letslocalhostand127.0.0.1through for testing. A browser sets those headers honestly, so this stops someone embedding your key on their own site. A script outside a browser can set any header it likes, so pair it with the protections below. - Honeypot field (every plan). A hidden field that people leave empty and bots fill in. A submission that fills it gets a normal success response but is discarded.
- CAPTCHA (reCAPTCHA, Turnstile, hCaptcha or ALTCHA). Once you turn one on, Static Forms verifies the token server-side, so a script that has the key but no valid token is rejected. reCAPTCHA v2 is on every plan; the others need Starter or above.
- Spam filter. Submissions that pass the checks above are still scored, and suspected spam goes to the Spam tab for review.
- Rate limits and quotas. The per-minute submission limit is shared by every form on your account, and the hourly limit is counted per API key. Submissions also count against your plan quota. See Rate Limits for the numbers.
- Key rotation. Rotate a form's key from its General settings. The old key stops accepting submissions immediately. See Rotating a key.
What to do
- Leave the key in your HTML. Do not build workarounds to hide it.
- Turn on a CAPTCHA (reCAPTCHA v2 on Free, any provider on Starter and above), and domain restriction if your plan includes it.
- Keep the honeypot field in the form.
- If a scanner flags the key, record it as an accepted public identifier.
- If you see abuse, rotate the key and update your HTML.
FAQ
Can someone read my submissions with the form key?
No. The key only identifies which form a submission is for. It does not sign anyone in, and it cannot read submissions or account data, or change settings. Reading your data needs a signed-in session, an OAuth connection or a private account key.
My security scanner flags the key as a hardcoded credential. Is it a leak?
No. Scanners match the pattern of a key sitting in source code (CWE-798). A form key has to sit in your HTML for the form to work, and it grants no access to your submissions or account. Mark the finding as accepted for this key, and keep real secrets such as CAPTCHA secret keys out of your HTML.
Can I keep the key out of my HTML?
Not while the browser posts directly to Static Forms. Anyone who opens the page source can see it. You can proxy the request through your own server, but then you run and maintain that server. Most sites leave the key in the HTML and use the protections below.
What if someone abuses my key?
Rotate it from the form's General tab. The old key stops accepting submissions immediately. Update your HTML with the new key right away.









