BUG REPORT · SVELTEKIT

Bug Report for SvelteKit

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 SvelteKit

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

§ 00SvelteKit + Bug Reportplatform-specific integration guide

Why SvelteKit developers choose splitforms for bug report

Svelte's lightweight runtime is one of its biggest selling points — adding a heavy form library defeats the purpose. The bug report on this page keeps that promise: it uses Svelte's native <code>on:submit</code> directive and a <code>fetch</code> POST, with no external dependencies. The form state lives in a simple <code>let</code> variable, not a store or a state machine. In SvelteKit, you could alternatively use a <code>+page.server.ts</code> action, but that couples your form to SvelteKit's server-side runtime — splitforms decouples it so the same form works on static hosts and other frameworks.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for SvelteKit.

Use the HTML snippet on this page, keep the bug report fields visible in your SvelteKit 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 sveltekit 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 × SvelteKitwhy this combination, in 80 words

Built for SvelteKit developers who hate operating a backend.

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

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

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

Drop the form snippet into a SvelteKit 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.

§ 03cSvelteKit production notesnative path · deploy · gotchas

What changes when this bug report lives in SvelteKit.

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

without splitforms

SvelteKit's headline form story is form actions — write a default-exported actions object in +page.server.ts, and SvelteKit handles FormData parsing, progressive enhancement (use:enhance), and result passing via the form prop. It's elegant DX — but it doesn't deliver email. You still write the SMTP integration, the spam-filter logic, the database for storing submissions, the webhook fan-out. The result is a form action that's ~80% boilerplate and ~20% your business logic. Splitforms collapses the boilerplate: the form posts directly from the browser to splitforms.com, the form action becomes a thin proxy (or you skip it entirely), and the operational layer disappears.

deploy notes

SvelteKit's adapter system is the deployment story: @sveltejs/adapter-vercel, -netlify, -cloudflare, -cloudflare-workers, -node, -static. The form's POST is cross-origin to splitforms regardless of adapter. On Cloudflare Pages/Workers (free tier: 10ms CPU per request), avoid Pattern B — the form action's fetch round-trip eats your budget; use Pattern A. On Vercel/Netlify, both patterns work with no measurable difference. $env/static/public inlines at build time (use for client-exposed keys); $env/static/private is server-only (use for Pattern B's server-action key). Domain-lock the access key.

SvelteKit gotcha

Form actions need POST and the named action prefix

If you use +page.server.ts form actions, the form's action attribute must be ?/contact (or whatever you named it) — not /api/contact. Forgetting the ?/ prefix routes to a 404 because SvelteKit doesn't recognize it as an action.

SvelteKit gotcha

use:enhance disables your client-side handler if you don't return a callback

use:enhance without arguments uses default progressive-enhancement behavior — which calls the form action and re-renders. If you need custom logic (toast on error, etc.), return a function: use:enhance={({ formData, cancel }) => async ({ result }) => …}.

SvelteKit gotcha

Cloudflare adapter has a 50ms cold start budget — fetch to splitforms eats it

If you use a SvelteKit form action that proxies to splitforms.com via fetch, the round-trip eats your CF Worker time budget on cold start. Skip the proxy: have the form POST directly to splitforms.com from the client (the snippet above does this).

SvelteKit gotcha

$env/static/public vs $env/dynamic/public — pick the right one

$env/static/public is inlined at build time (faster, but key is in the bundle). $env/dynamic/public is read at runtime (slower, but rotatable without rebuild). For the splitforms key, static is fine if you've locked the key to your domain.

PATTERN A

Pattern A — client-side fetch (skip form actions)

Pure +page.svelte with a fetch handler — no +page.server.ts needed. Simpler, works on every adapter without server CPU time, no proxying. Best for Cloudflare Workers / Pages where CPU budget matters. Use the same wiring for the bug report fields on this page.

pattern-a.txtsvelte14 lines

01<script>
02  let status = "idle";
03  async function onSubmit(e) {
04    status = "loading";
05    const fd = new FormData(e.currentTarget);
06    fd.append("access_key", import.meta.env.VITE_PUBLIC_SPLITFORMS_KEY);
07    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
08    status = (await r.json()).success ? "ok" : "err";
09  }
10</script>
11<form on:submit|preventDefault={onSubmit}>
12  <input name="email" type="email" required />
13  <button disabled={status === "loading"}>Send</button>
14</form>

PATTERN B

Pattern B — form action with use:enhance (no-JS support)

Server-side form action proxies to splitforms; key stays in $env/static/private. With use:enhance, the form posts traditionally without JS (full-page reload, splitforms 302 to /thanks) and AJAXes when JS loads. Maximum compatibility, slight CPU cost on the server. Use the same wiring for the bug report fields on this page.

pattern-b.txtsvelte12 lines

01// +page.server.ts
02import { fail, redirect } from "@sveltejs/kit";
03import { SPLITFORMS_KEY } from "$env/static/private";
04export const actions = {
05  default: async ({ request }) => {
06    const fd = await request.formData();
07    fd.append("access_key", SPLITFORMS_KEY);
08    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09    if (!(await r.json()).success) return fail(400, { message: "Failed" });
10    throw redirect(303, "/thanks");
11  },
12};

§ 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 SvelteKit — FAQ.

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

01Does this bug report work on SvelteKit?

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

02How much does the bug report cost on SvelteKit?

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 SvelteKit 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 SvelteKit 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 SvelteKit5 adjacent patterns

Ship a bug report on SvelteKit in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Bug Report for SvelteKit

Why SvelteKit developers choose splitforms for bug report

Yes — this is the shortest safe path for SvelteKit.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for SvelteKit developers who hate operating a backend.

Drop into any SvelteKit project.

Generate, embed, receive.

Generate a free splitforms key

Paste the bug report into your SvelteKit 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 SvelteKit.

Form actions need POST and the named action prefix

use:enhance disables your client-side handler if you don't return a callback

Cloudflare adapter has a 50ms cold start budget — fetch to splitforms eats it

$env/static/public vs $env/dynamic/public — pick the right one

Pattern A — client-side fetch (skip form actions)

Pattern B — form action with use:enhance (no-JS support)

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 SvelteKit — FAQ.

splitforms vs everything else.

Other ready-to-ship SvelteKit forms.

Ship a bug report on SvelteKit in 60 seconds.