Skip to content
Docs menu

Share a form and take responses

The public form page, embeds (inline, popup, slider), file uploads, hidden fields from the link, and the local spam defences that need no third-party CAPTCHA.

View .md

A published form lives at https://<your cloud>/f/<slug>. Nobody signs in to answer it. The Share tab shows the link, the embed codes and a QR code.

The public page

  • What it shows. The published version only: not your draft, not your destinations, retention or other settings, and nothing else about your organisation. A draft or an unknown link is a plain "not found". A closed form, one past its close date and one that reached its response limit say so and take nothing.
  • How it behaves. One question at a time (Enter moves on, letters pick choices) or a classic page, per the form's setting. Labels, error messages and keyboard use follow WCAG 2.2. It loads no web font, no third-party script and no analytics, and its Content Security Policy allows only this cloud's own origin (connect-src 'self'; the page can still be framed on any site, which is what an embed is). It is never indexed.
  • How light it is. The server renders the whole page as HTML. The only script is /f/runtime.js, plain JavaScript with no framework: about 37 KB (11 KB gzipped), and a test fails if it grows past 50 KB. It runs your form's logic with the same code the server uses to check a submit, so the page accepts what the server accepts. It carries every question type, the checks, file uploads, drop-off counts, the proof of work and the handshake with the embed script. Light and dark follow the respondent's system. The page used to ship the app's React runtime (over 300 KB gzipped).
  • Hidden fields. A hidden-field block is filled from the link: ?utm_source=newsletter. The block's parameter name is shown in Share.
  • A logo. Settings → Appearance takes a PNG, JPEG, WebP or GIF up to 512 KB and shows it above the form. It is served publicly at /f/<slug>/logo, and only that file is.

Embeds

Add the script once; it comes from your own cloud (/f/embed.js, about 3 KB, no dependencies).

<!-- inline, sized to the form -->
<div data-venom-form="my-form-1a2b" data-height="600"></div>
<!-- a popup or a slider from a button -->
<button data-venom-form-open="my-form-1a2b" data-venom-form-mode="popup">Open the form</button>
<script src="https://cloud.example.com/f/embed.js" async></script>

data-hidden-<name>="value" on either element fills a hidden field. From code: VenomForms.popup("my-form-1a2b"), VenomForms.slider("my-form-1a2b"), VenomForms.close(). The page tells the script its height by postMessage; the script listens only to messages from the origin it was loaded from. A submitted form fires venom-forms:submitted on document. Escape closes a popup and focus returns to the button.

A plain iframe works too: <iframe src="…/f/<slug>?embed=1">.

File uploads

A file-upload question takes files up to its size limit (10 MB by default, 100 MB at most) and, if you set them, its types (.pdf, image/*). They use the chunked upload of Venom Notes, so large files work and the org's file quota applies. The Notes add-on must be on. Files are staged against the page the respondent opened and attached when they submit; ones never submitted are removed by the sweep within a day. Only someone who can read the form's responses can download a file (in the Responses tab or through /forms/api/v1/forms/{id}/files/{fileId}), always as a download, never inline. The file route of Notes never serves them.

Spam, without a CAPTCHA

Everything runs in your cloud:

  • A trap field no person sees; a bot that fills every input fills it, is told "ok" and is dropped.
  • A minimum time (Settings → Spam protection, 2 seconds by default) between opening and submitting.
  • Proof of work, optional per form (Settings → Spam protection → Proof of work). The page solves a small hash puzzle on its respondent token while the person fills the form (about a second of CPU), and the submit carries the answer. Nothing leaves the page and no third party is involved; a script posting thousands of submits pays that second every time. A form that asks for it refuses a submit without a valid answer.
  • Rate limits per form and per visitor: 10 submits a minute per visitor, 300 a minute per form, 60 opens, 30 uploads. The visitor is a keyed hash of the address with a salt that changes every UTC day; the address is never stored, and the hash only lives in a one-minute window.
  • Size caps. A response is at most 256 KB; text answers are capped by type; a response is checked against the form's own rules on the server, whatever the page sent.

A response records the version the page showed, and is validated against that version, so publishing a change while someone is answering does not break their submit.

What the server counts

Views (the page opened), starts (the first step), questions reached (for the drop-off chart) and submits are counted per hour. Partial answers are not stored, only how far someone got. See responses.