Free bug report form template
Report the problem first and add the detail after, across three short steps.
- 9 questions
- Multi-step
- 1 conditional
- Free, unlimited responses
Opens in your dashboard with the whole form in front of you. Nothing is created until you say so. Keep it, restyle it, or pick a different one.
Updated October 7, 2026
- What happened
Step 1 of 3
Try it in another theme
Ships in Terminal · 26 to choose from
Tap any theme to see this form wearing it.
What this bug report form asks, and why
Someone reporting a bug is already frustrated, so the first step asks only what went wrong. The second step asks what they expected, how badly it affects them and how often it happens. Reproduction steps are requested only for bugs that happen every time, because a one-off rarely has steps to give. The third step asks where it happened (web, mobile web, iOS, Android or elsewhere), invites a screenshot or recording, and collects an email, plus permission to follow up. Severity and frequency together sort your queue. On Pro, a webhook can open an issue in your tracker for each report.
- Questions
- 9, 4 required, 1 conditional
- Format
- Multi-step
- Theme
- Terminal, or any of 26
- Cost
- Free, no response cap
The 9 questions it asks
In order, with their field types and why each one is there. Pick one to see its screen above. Edit, reorder or delete any of them once it's yours.
Alone on the first step, so people say what they came to say before anything else is asked.
The gap between expected and actual behavior is often what separates a bug from a misunderstanding.
How badly it affects them, the first thing a support team uses to order its queue.
Every time, sometimes or once. The answer decides whether reproduction steps are asked for.
Shown only for bugs that happen every time. A one-off rarely has reproducible steps, so nobody else is asked.
Web, mobile web, iOS, Android or elsewhere. Edit the list to the platforms you ship.
A screenshot or recording, often worth more than the written description.
Required, so the team can ask a follow-up question or confirm the fix.
Permission to follow up, so engineers know who is happy to help investigate.
1 question is conditional. It only appears when an earlier answer calls for it, so most people answer 8, not 9.
Built for these jobs, and easy to bend to yours
- Product bug reports
- Beta feedback
- Internal QA
- Customer support intake
Ways to adapt it
Internal QA
Add a dropdown for the build or release version and a field for the tester's name, for teams testing before launch.
Embedded in your app
Embed the form in your help menu so reports arrive from inside the product, where the problem was seen.
Feature requests alongside
Add a first question asking whether it is a bug or an idea, and show a separate set of questions for ideas.
How to get good answers from a bug report form
- 1
Make the first step easy
Someone reporting a bug is already frustrated. Asking only 'what went wrong' first gets the report submitted before patience runs out.
- 2
Encourage screenshots
Say in the upload question that a screenshot speeds up the fix. A picture of the error removes most of the back-and-forth.
- 3
Acknowledge every report
Use the ending screen to say what happens next and roughly when. Silence after a bug report reads as indifference.
- 4
Triage on severity and frequency
A bug that blocks work every time comes before an annoyance that happened once. Reading the two answers together sorts the queue.
After you publish
Where the responses go next
Open an issue automatically
On Pro, a signed webhook or a Zapier or Make step can create an issue in your tracker from each report.
Alert the on-call engineer
On Pro, post every report to an engineering Slack channel so 'Can't work at all' reports are seen at once.
Spot repeat problems
Search the responses for a feature name or error message to find every report of the same issue.
Bug Report Form: common questions
Still deciding?
Seven steps from an empty account to a published form.
What should a bug report form include?
What went wrong, what was expected, how severe it is, how often it happens, where it happened, a screenshot, and a way to follow up. This template asks for each across three short steps.
Why are reproduction steps not always asked?
They appear only when someone says the bug happens every time. For a one-off bug there are usually no reliable steps to give.
Can people attach screenshots or recordings?
Yes. The upload question accepts files up to 5 MB each on the free plan and 10 MB on paid plans.
Can it create tickets in our issue tracker?
On Pro, use a signed webhook or Zapier or Make to create an issue from each report in most trackers.
Can someone save a report and finish it later?
Yes. As a multi-step form it has a 'Save & continue later' button, though most reports are finished in one go.
Related templates
- Refund RequestA short refund request, one question a screen, starting with the order number.6 questions · One question at a time
- Cancellation SurveyWhy they're leaving, asked once and plainly, with no save offer.5 questions · One question at a time
- Contact FormLet visitors reach you with four fields and nothing in the way.4 questions · Single page
Ready to create forms people actually answer?
Beautiful forms, unlimited responses, and real insight, all free to start. No credit card, no catch.
Free forever · or explore templates first