Forms overview

Forms are first-class in PageFork. You don’t install a third-party widget, paste embed codes, or configure webhooks — you just ask, and submissions appear in your inbox.

Adding a form

Open the editor and say what you want:

• “Add a contact form with name, email, and message.”
• “Put a newsletter signup form (just email) in the footer.”
• “Add a waitlist form with name, email, and company — make email required.”

PageFork:

• Generates the form UI in the right section.
• Connects it to PageFork’s form backend for this site.
• Sends you an email notification on each submission.
• Stores each submission in the Submissions inbox.

Forms vs third-party tools

If you already use Mailchimp, HubSpot, ConvertKit, Typeform, Tally, or similar, you can embed them instead — see Embeds and iframes for the patterns.

Reach for a third-party form when you need features PageFork’s built-in forms don’t cover: branching logic, calculations, payment fields, or direct routing into another tool (Notion, Airtable, Sheets) without custom plumbing. For everything else, PageFork’s built-in forms are the simpler default — one less service to manage.

Required vs optional fields

Tell PageFork which fields are required:

• “Make email required, everything else optional.”
• “Require all fields.”

Client-side validation is automatic: empty required fields block submission.

Privacy

PageFork stores:

• The values submitted.
• The submission timestamp.
• The submitter’s IP address (for anti-spam / legitimacy checks).
• The Origin header of the page that submitted.

That’s it. If you need to comply with a privacy policy (GDPR, CCPA), add a clear disclosure to your form (“By submitting, you agree to our privacy policy”) and publish a matching policy page.

Limits

• No artificial cap on submissions per form.
• Anonymous submissions are rate-limited to prevent abuse.
• For extremely high-volume lead capture, contact support.

Next

• Submissions inbox
• Email notifications
• CSV export
• Form field schemas