Framework guide

Contact form for Hugo without a backend

Hugo can render the form into a page or partial; submission handling happens outside your generated site.

Where this goes

Save as layouts/partials/contact.html and include it with {{ partial "contact.html" . }}.

Create a form in the dashboard and replace YOUR_FORM_ID with your endpoint ID. No account key belongs in this code.

<form action="https://formdrop.wouldairecommend.workers.dev/f/YOUR_FORM_ID" method="POST">
  <label for="email">Email</label>
  <input id="email" type="email" name="email" required>
  <label for="message">Message</label>
  <textarea id="message" name="message" required></textarea>
  <input name="_gotcha" tabindex="-1" autocomplete="off" hidden>
  <button type="submit">Send message</button>
</form>

The detail that matters

Use an absolute endpoint URL so language prefixes and nested page paths do not change the target.

After you publish

Send a test from the published page, then check Inbox and Spam. Native forms follow a redirect; fetch clients must request JSON and show errors. Set your allowed domains to the hostnames you actually publish, including any preview hostname you need.

Read the endpoint reference for reserved fields, CORS and redirect rules. Start from the accessible contact template if you need styling.

Questions about this setup

Does Hugo need its own backend?
No. The browser posts the named form fields to your FormDrop endpoint. Your site can stay static.
Will this send an email notification?
Email notifications are not switched on yet. Read submissions in the dashboard or connect Slack, Discord, Telegram or a webhook.
Can I attach a file?
File uploads: not yet. Text fields are saved; files are ignored and flagged in the dashboard. Link to an existing public document instead.