BUG REPORT · WEBFLOW

Bug Report for Webflow

Bug reports with severity, environment, and reproduction steps. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Webflow

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New bug report">
04 
05  <label for="title">Short summary *</label>
06  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
07  <label for="severity">Severity *</label>
08  <select id="severity" name="severity" required>
09    <option value="">Choose…</option>
10    <option>Critical</option>
11    <option>High</option>
12    <option>Medium</option>
13    <option>Low</option>
14  </select>
15  <label for="browser">Browser &amp; OS</label>
16  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
17  <label for="steps">Steps to reproduce *</label>
18  <textarea id="steps" name="steps" placeholder="1. Go to…
192. Click…
203. See error" required></textarea>
21  <label for="email">Your email (so we can follow up) *</label>
22  <input id="email" type="email" name="email" placeholder="you@example.com" required>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Webflow + Bug Reportplatform-specific integration guide

Why Webflow developers choose splitforms for bug report

Webflow's built-in form block sends to Webflow's own backend, which caps at 100 submissions/month on the free plan and lacks webhook delivery, CC recipients, and spam filtering. The bug report on this page bypasses that entirely — paste it into a custom embed element, set the form action to splitforms, and you get 500 dashboard submissions/month with AI spam filtering; Starter adds Slack/Discord webhooks. Webflow's native interactions (success message, loading state) still work if you use <code>fetch</code> instead of a native form submit.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Webflow.

Use the HTML snippet on this page, keep the bug report fields visible in your Webflow UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains short summary, severity, browser & os, steps to reproduce, your email (so we can follow up). Required fields are short summary, severity, steps to reproduce and your email (so we can follow up).

native webflow reality

use case fit

User-reported bugs are signal — but only if the report has steps-to-reproduce and a screenshot. The form forces the structure, then files the issue automatically.

§ 01Bug Report × Webflowwhy this combination, in 80 words

Built for Webflow developers who hate operating a backend.

Splitforms is the form backend for Webflow sites. One POST endpoint, no SDK, no plugin — drop the bug report into a page and ship.

Splitforms is the form backend for Webflow sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codeHTML · 28 lines

Drop into any Webflow project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Webflow page, and ship. No build-time integration required.

form.htmlhtml28 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New bug report">
04 
05  <label for="title">Short summary *</label>
06  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
07  <label for="severity">Severity *</label>
08  <select id="severity" name="severity" required>
09    <option value="">Choose…</option>
10    <option>Critical</option>
11    <option>High</option>
12    <option>Medium</option>
13    <option>Low</option>
14  </select>
15  <label for="browser">Browser &amp; OS</label>
16  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
17  <label for="steps">Steps to reproduce *</label>
18  <textarea id="steps" name="steps" placeholder="1. Go to…
192. Click…
203. See error" required></textarea>
21  <label for="email">Your email (so we can follow up) *</label>
22  <input id="email" type="email" name="email" placeholder="you@example.com" required>
23 
24  <!-- honeypot — bots fill every field -->
25  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
26 
27  <button type="submit">Send</button>
28</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first bug report submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the bug report into your Webflow project

Drop the form snippet into a Webflow page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New bug report

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bBug Report Form (Issue Submission)template-specific playbook

The reason this bug report exists.

Screenshot upload (Pro) · webhooks into Linear / GitHub Issues / Slack.

why it matters

Bug reports without reproduction steps waste hours of triage. The form structures the report — what happened, what was expected, steps to reproduce, browser / OS / device, screenshot. Screenshot upload is critical: 'the page broke' tells you nothing; a screenshot of the broken state tells you everything. Webhook the structured report into Linear or GitHub Issues so it lands as a triageable ticket, not a Slack message that scrolls away. For SaaS teams the time saved is huge — instead of a 4-message back-and-forth gathering basic context, the engineer opens the issue and starts debugging.

route the submission

Structure the report

Required: what happened, what you expected, steps to reproduce. Optional: browser, OS, device, URL where it occurred. Most templates auto-detect browser/OS via JS so the user doesn't have to fill them.

Screenshot upload

Pro file upload — drag-and-drop a screenshot or screen recording. Multi-file accepted. Image attachments arrive on the email and via webhook with signed URLs.

Webhook into Linear / GitHub

Lands as a Linear issue or GitHub issue with the structured report as the body and the screenshot embedded. Engineer opens, reproduces, fixes — no triage thread needed.

§ 03cWebflow production notesnative path · deploy · gotchas

What changes when this bug report lives in Webflow.

These notes come from the Webflow platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Webflow's built-in Forms feature delivers submissions to your Webflow project dashboard and emails them — but the free Site plan caps submissions (50 per site, lifetime, on legacy plans) and webhooks are gated behind the Workspace plan ($24/mo+). Worse, the form fails silently if you exceed the cap: users see the 'success' state, your inbox gets nothing. There's no API to inspect submissions programmatically below the Workspace tier, and CMS-driven forms inherit the same caps. Native is fine for a personal portfolio with three submissions a year; for any real lead capture, you need an external endpoint. Splitforms is that endpoint without the plan upgrade.

deploy notes

Webflow hosts your published site on its own CDN — there's no Vercel/Netlify config to worry about. The form posts cross-origin to splitforms regardless. Disable Webflow's built-in hCaptcha for the form (Form Settings → Spam Filter → Off) — it intercepts submissions client-side before splitforms is reached. Lock the splitforms access key to BOTH your *.webflow.io staging URL and your custom domain in the dashboard; Webflow serves both, with different Origin headers. Custom code embeds count toward Webflow's per-page code limit (10 KB) — keep raw-HTML Embed forms tight if you have multiple per page.

Webflow gotcha

Webflow strips custom hidden inputs from native Form Blocks

If you add <input type="hidden" name="access_key"> directly in Designer's Form Block, Webflow ignores it on publish. Use the Form Block's settings panel: Form Settings → Form Name + add custom attribute. Or use an Embed element with raw HTML if you need full control.

Webflow gotcha

Default action URL gets reset on every Designer save

Setting the Action URL to https://splitforms.com/api/submit in the Form Block sometimes reverts to Webflow's default after a publish. The fix: lock it in by adding a custom attribute action to the form element (Settings → Element Settings → Custom Attribute).

Webflow gotcha

Method must be set to POST in the form's settings, not the URL

Webflow forms default to GET. Open the form's Settings panel, change Method to POST. If you forget, the submission posts your fields as URL query params — splitforms returns a 405 Method Not Allowed.

Webflow gotcha

Webflow's success/error elements still trigger on AJAX submit

Webflow auto-shows the .w-form-done div on a 2xx response. That's good — but if you also set up a redirect field in splitforms, the user sees the success message for ~80ms before the redirect fires. Either remove the success div or skip the redirect field.

PATTERN A

Pattern A — native Form Block with overridden action URL

Use Webflow's drag-and-drop Form Block — keep the styling, structure, and Designer integration. In Form Settings, change Action to https://splitforms.com/api/submit and Method to POST. Add a hidden access_key field via the form's settings panel. Submissions skip Webflow's backend entirely. Use the same wiring for the bug report fields on this page.

pattern-a.htmlhtml8 lines

01<!-- After saving in Designer, the published HTML looks like: -->
02<form action="https://splitforms.com/api/submit" method="POST">
03  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04  <input type="text"  name="name" required />
05  <input type="email" name="email" required />
06  <textarea name="message" required></textarea>
07  <input type="submit" value="Send" />
08</form>

PATTERN B

Pattern B — Embed element with raw HTML

If you need full control over markup (custom honeypot, file upload, multi-step), drop an Embed element on the canvas with raw HTML. Skips Webflow's form widget entirely. Useful for forms that don't fit the Designer's mental model. Use the same wiring for the bug report fields on this page.

pattern-b.htmlhtml8 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect" value="/thanks" />
04  <input name="email" type="email" required />
05  <textarea name="message" required></textarea>
06  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
07  <button type="submit">Send</button>
08</form>

§ 04Field-by-field rundown5 fields · names you POST

What every field actually does.

Each field below ships in the bug report template — rename, remove, or add your own. Splitforms accepts any name you POST.

titleREQUIRED

TEXT

Short summary

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

placeholder · What went wrong?

severityREQUIRED

SELECT

Severity

Triage signal — drives whether this pages on-call or waits till Monday.

CriticalHighMediumLow

browser

TEXT

Browser & OS

Repro context for engineering — saves a back-and-forth.

placeholder · Chrome 120 / macOS

stepsREQUIRED

TEXTAREA

Steps to reproduce

Free-text input — no character limit, expands as the visitor types.

placeholder · 1. Go to… 2. Click… 3. See error

emailREQUIRED

Your email (so we can follow up)

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

§ 05Bug Report on other frameworks21 frameworks · same backend

One backend. Every framework.

The same bug report template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Bug Report on Webflow — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this bug report work on Webflow?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Webflow site without server-side code, plugins, or SDKs. Drop the snippet into a Webflow page or component and submissions land in your splitforms dashboard.

02How much does the bug report cost on Webflow?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (short summary, severity, browser & os, steps to reproduce…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the bug report?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Webflow as on any other framework.

05Can I send the bug report submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Webflow site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I auto-detect browser / OS?

Yes — JavaScript can read navigator.userAgent and pre-fill hidden fields with browser name, version, OS, and screen size. The user doesn't see them; the engineer gets them. Saves 90% of 'what browser are you on?' replies.

08Can I integrate with Linear / GitHub / Sentry?

Yes — webhook the JSON. Linear and GitHub both accept inbound issue creation via API or Zapier. Sentry doesn't accept user-reported bugs as events but you can webhook to a Slack channel where the on-call engineer triages and creates the Sentry issue manually.

09How do I prevent abuse / spam in bug reports?

Public bug-report forms attract spam — hidden honeypot plus splitforms' classifier catches most. Require an email field; bots filling random emails get filtered by the classifier. For severe abuse, gate the form behind a logged-in user session.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Webflow5 adjacent patterns

Ship a bug report on Webflow in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Webflow project.

Get free access key →Read the docs

founders pricing locked in · early access open

Bug Report for Webflow

Why Webflow developers choose splitforms for bug report

Yes — this is the shortest safe path for Webflow.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Webflow developers who hate operating a backend.

Drop into any Webflow project.

Generate, embed, receive.

Generate a free splitforms key

Paste the bug report into your Webflow project

Receive submissions

The reason this bug report exists.

Structure the report

Screenshot upload

Webhook into Linear / GitHub

What changes when this bug report lives in Webflow.

Webflow strips custom hidden inputs from native Form Blocks

Default action URL gets reset on every Designer save

Method must be set to POST in the form's settings, not the URL

Webflow's success/error elements still trigger on AJAX submit

Pattern A — native Form Block with overridden action URL

Pattern B — Embed element with raw HTML

What every field actually does.

Short summary

Severity

Browser & OS

Steps to reproduce

Your email (so we can follow up)

One backend. Every framework.

Bug Report on Webflow — FAQ.

splitforms vs everything else.

Other ready-to-ship Webflow forms.

Ship a bug report on Webflow in 60 seconds.