Where should a Jekyll form endpoint live?

Put it in _config.yml, an environment-specific config, or _data, then render it through a Liquid include.

Can Jekyll forms upload files?

Yes. Add enctype="multipart/form-data" and a named file input to the generated form.

What can break a Jekyll contact form?

Themes or plugins can strip form attributes. Always inspect the generated _site HTML before publishing.

Does Form Plume work with Jekyll?

Yes. Form Plume gives you one endpoint that works from your Jekyll site. Start with the quickstart docs, then drop the endpoint into your form.

Where do Jekyll form submissions go in Form Plume?

Submissions are stored in your Form Plume dashboard, sent to your email, and can trigger integrations like webhooks, Slack, Discord, Google Sheets, Mailchimp, and ActiveCampaign. See the feature overview for the full flow.

Can I try Form Plume before wiring it into my Jekyll site?

Yes. You can create an endpoint on the free plan, test it from localhost, preview, or a staging URL, and upgrade only when your form volume or team needs grow. Compare limits on pricing or ask a question on the contact page.

New:Build with AI agents

Jekyll contact forms
without Ruby mail code.

Keep your Jekyll site static and point the generated form at Form Plume for email notifications, dashboard storage, spam filtering, file uploads, integrations, and signed webhooks.

Free foreverNo credit cardJekyll endpoint ready in under a minute

_includes/contact-form.html

<form action="{{ site.formplume_endpoint }}" method="POST">
  <input type="hidden" name="source" value="jekyll">
  <input name="name" autocomplete="name" required>
  <input name="email" type="email" autocomplete="email" required>
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

The full guide

A hosted backend for Jekyll includes.

Use Liquid includes and config values to generate a plain form that works from GitHub Pages or any static host.

1
Create your Form Plume accountStart free and give your Jekyll form a hosted endpoint for email, submissions, spam filtering, uploads, integrations, and webhooks.Start free
2
Create the form and copy the endpointCopy the endpoint URL from Form Plume. It looks like https://api.formplume.com/f/your-slug
3
Connect it inside JekyllPut the endpoint in Jekyll config or data, render it through a Liquid include, build the site, and inspect the _site output. Send one test submission from the real Jekyll app or preview environment and confirm it reaches Form Plume.

You can use this AI prompt to hand the platform-specific wiring to an assistant without accidentally creating a backend.

You are helping me integrate a Jekyll contact form with Form Plume.

Important:
- Do not create a Form Plume account or form for me.
- If I have not provided a Form Plume endpoint yet, stop and ask me for it.
- Tell me to get the endpoint by signing up at https://formplume.com/signup, creating a form, copying the endpoint URL, and pasting it back into this chat.
- Only update code after I provide the endpoint or explicitly confirm the placeholder should stay.

FORM_PLUME_ENDPOINT="PASTE_YOUR_FORM_PLUME_ENDPOINT_HERE"

After the endpoint is available:
- Set the form action or submission target to FORM_PLUME_ENDPOINT.
- Use method="POST" for a plain HTML form.
- Do not add a custom backend, database table, SMTP client, PHP mail handler, serverless function, or email provider.
- Preserve the existing visual styling unless I ask you to improve it.
- Make sure every input, textarea, and select that should be submitted has a name attribute.
- Use clear field names such as name, email, message, company, phone, subject, budget, page, source, and attachment.
- If the form includes files, use enctype="multipart/form-data".
- If I want a custom success page, add a hidden _redirect field with the URL or path I provide.
- Follow this implementation guidance: use a Liquid include, _config.yml or _data for the endpoint, generated _site verification, named fields, and no Ruby mail handler.
- Preserve the existing component, template, or page styling unless I ask you to improve it.
- Keep labels, validation, pending states, success states, and error states accessible.
- Use FormData when the form includes files or may add files later.

After implementation, tell me exactly which file or editor area changed, where the endpoint is configured, and how to test one real submission.

Use a Liquid include

Jekyll sites should keep shared form markup in _includes/contact-form.html. The final output is plain HTML, but the include keeps the endpoint and fields consistent across pages.

<form action="{{ site.formplume_endpoint }}" method="POST">
  <input type="hidden" name="source" value="jekyll">
  <input type="hidden" name="_redirect" value="/thanks/">
 
  <label for="contact-name">Name</label>
  <input id="contact-name" name="name" autocomplete="name" required>
 
  <label for="contact-email">Email</label>
  <input id="contact-email" type="email" name="email" autocomplete="email" required>
 
  <label for="contact-message">Message</label>
  <textarea id="contact-message" name="message" rows="5" required></textarea>
 
  <button type="submit">Send message</button>
</form>

Render the include from a page or layout.

{% include contact-form.html %}

Configure the endpoint once

Add the endpoint to _config.yml, an environment-specific config file, or a data file if your build pipeline prefers _data.

formplume_endpoint: "PASTE_YOUR_FORM_PLUME_ENDPOINT_HERE"

Run bundle exec jekyll build, then inspect _site/contact/index.html. You should see a normal form with the real endpoint in the action.

No Ruby server required

After deployment, Jekyll is just static HTML. You do not need mail, Net::SMTP, a plugin, a serverless function, or a database for the contact form. Form Plume receives the browser POST and handles email notifications, storage, spam filtering, uploads, integrations, and webhooks.

Uploads

File uploads use the same HTML you would write anywhere else.

<form
  action="{{ site.formplume_endpoint }}"
  method="POST"
  enctype="multipart/form-data"
>
  <input type="file" name="attachment" accept=".pdf,.png,.jpg">
  <button type="submit">Send file</button>
</form>

If a theme wraps your content, inspect the built _site HTML to make sure the theme did not strip method, action, enctype, or hidden fields.

Primary sources

FAQ

Jekyll form questions
before deploy.

Yes. GitHub Pages serves static HTML, and the browser can post that form directly to Form Plume.

One line. Zero backend.

The form backend you don’t have to build.

Free foreverNo credit cardSet up in under a minute

Jekyll contact forms without Ruby mail code.