splitforms.com
BUG REPORT · NETLIFY

Bug Report for Netlify

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

500/mo free·no card·drop-in for Netlify
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
5
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Netlify + Bug Reportplatform-specific integration guide

Why Netlify developers choose splitforms for bug report

Netlify Forms are the obvious choice for Netlify-hosted sites, but they're limited to 100 submissions/month on the free plan, 1,000 on paid, and they don't include webhook delivery, CC recipients, or AI spam filtering on any tier. The bug report on this page works with or without Netlify Forms — it posts directly to splitforms, bypassing Netlify's form handler. You keep Netlify for hosting, CDN, and deploys while splitforms handles the form pipeline independently. This also means your form works if you migrate to Vercel, Cloudflare Pages, or any other host.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Netlify.

Use the HTML snippet on this page, keep the bug report fields visible in your Netlify 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 netlify reality

Netlify can render the form markup, but it still needs a backend endpoint, email delivery, spam checks, and webhook routing before submissions are useful.

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 × Netlifywhy this combination, in 80 words

Built for Netlify developers who hate operating a backend.

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

Splitforms is the form backend for Netlify 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 Netlify project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Netlify 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

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the bug report into your Netlify project

Drop the form snippet into a Netlify 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
01

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.

02

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.

03

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.

§ 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
EMAIL

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
§ 06Questions9 answered

Bug Report on NetlifyFAQ.

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

01Does this bug report work on Netlify?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Netlify site without server-side code, plugins, or SDKs. Drop the snippet into a Netlify page or component and submissions land in your splitforms dashboard.
02How much does the bug report cost on Netlify?
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 Netlify 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 Netlify 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.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a bug report on Netlify in 60 seconds.

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

Get free access key →Read the docs
founders pricing locked in · early access open