BUG REPORT · CARRD

Bug Report for Carrd

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 Carrd

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

§ 00Carrd + Bug Reportplatform-specific integration guide

Why Carrd developers choose splitforms for bug report

Carrd's embed element lets you inject custom HTML into your one-page site — perfect for a lightweight contact form. Carrd Pro includes a native form feature, but it caps submissions at 100/month on paid plans and lacks webhook delivery. The bug report on this page drops into a Carrd embed, posts to splitforms, and gives you 500 dashboard submissions/month free; Starter adds Slack/Discord notifications. No Carrd Pro upgrade needed for the form to work. The HTML is self-contained — Carrd's minimal runtime handles the display, splitforms handles the backend.

§ 00Quick answerHTML · support

Yes — this is the shortest safe path for Carrd.

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

Built for Carrd developers who hate operating a backend.

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

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

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

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

§ 03cCarrd production notesnative path · deploy · gotchas

What changes when this bug report lives in Carrd.

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

without splitforms

Carrd's Form widget requires Pro Standard ($19/year) just to exist on the page, and even then it doesn't deliver email itself — the form 'works' by posting to an external integration: Mailchimp, SendGrid, Basin, Formspree, etc. So the question isn't 'native vs splitforms' but 'which third-party backend do you wire up?'. Mailchimp is overkill (and surprisingly expensive once your list grows); Basin and Formspree limit free submissions; SendGrid requires DNS verification. Splitforms is the same shape of integration (Type: Custom, Method: POST, Action: a URL) at a better free tier and with built-in spam filtering. Carrd's Form widget settings don't change.

deploy notes

Carrd publishes to a *.carrd.co subdomain on every plan; Pro Standard adds a custom domain. The form posts to splitforms from the browser, so neither subdomain nor custom domain matters for delivery. Lock the splitforms access key to BOTH the *.carrd.co URL and your custom domain — Carrd serves the same content under both, with different Origin headers. Carrd's Designer preview never actually POSTs; you have to publish (free) and submit from the live URL to test. Embed elements bypass Carrd's CSS, so the form will look browser-default unless you inline styles.

Carrd gotcha

Pro Standard plan still required for Custom form Type

Carrd's free plan and Pro Lite don't expose the Form widget at all. Pro Standard ($19/yr) unlocks the Form widget with Type → Custom. Splitforms doesn't change Carrd's plan requirements — it just fills in the backend that Carrd doesn't ship.

Carrd gotcha

Embed element forms don't inherit Carrd's site styles

If you paste raw HTML via an Embed element, your form will look like browser-default — no Carrd typography, no site colors. Use the native Form widget for styling, then add a hidden access_key field via Custom fields.

Carrd gotcha

Carrd's success message + splitforms redirect can fight each other

Carrd's Form widget has a built-in success message that shows on 2xx response. If you also set a redirect field in the form, the user sees the success blip then redirects mid-message. Pick one: redirect via splitforms OR Carrd's success text.

Carrd gotcha

The form widget's Field labels don't match input names by default

Carrd uses friendly labels like 'Your name', but the actual input name attribute is name-1 or similar unless you set Custom in the field settings. Set the Custom name to name, email, message — splitforms uses the input names as keys in your inbox.

PATTERN A

Pattern A — native Form widget set to Custom type

In the Form widget's settings, set Type to Custom, Method to POST, Action to the splitforms URL. Add a hidden field access_key via the Custom Fields tab. Carrd handles the styling and mobile layout; splitforms handles delivery. Use the same wiring for the bug report fields on this page.

pattern-a.htmlhtml8 lines

01<!-- Carrd auto-generates this on publish: -->
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" placeholder="Name" required />
05  <input type="email" name="email" placeholder="Email" required />
06  <textarea name="message" placeholder="Message" required></textarea>
07  <button type="submit">Submit</button>
08</form>

PATTERN B

Pattern B — Embed element with full HTML control

Drop an Embed element into a Carrd section and paste raw HTML. Loses Carrd's auto-styling but lets you add a honeypot, multi-field validation, or custom redirect. Useful for waitlist or job-application forms that exceed the Form widget's capability. Use the same wiring for the bug report fields on this page.

pattern-b.htmlhtml9 lines

01<form action="https://splitforms.com/api/submit" method="POST" style="display:grid;gap:8px;max-width:380px;">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect" value="/thanks" />
04  <input name="name" placeholder="Name" required />
05  <input name="email" type="email" placeholder="Email" required />
06  <textarea name="message" placeholder="What's up?" required></textarea>
07  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
08  <button type="submit">Send</button>
09</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 Carrd — FAQ.

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

01Does this bug report work on Carrd?

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

02How much does the bug report cost on Carrd?

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 Carrd 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 Carrd 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 Carrd5 adjacent patterns

Ship a bug report on Carrd in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Bug Report for Carrd

Why Carrd developers choose splitforms for bug report

Yes — this is the shortest safe path for Carrd.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Carrd developers who hate operating a backend.

Drop into any Carrd project.

Generate, embed, receive.

Generate a free splitforms key

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

Pro Standard plan still required for Custom form Type

Embed element forms don't inherit Carrd's site styles

Carrd's success message + splitforms redirect can fight each other

The form widget's Field labels don't match input names by default

Pattern A — native Form widget set to Custom type

Pattern B — Embed element with full HTML control

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

splitforms vs everything else.

Other ready-to-ship Carrd forms.

Ship a bug report on Carrd in 60 seconds.