Bug Reporting for Webflow

The bug reporting widget for Webflow sites

Client reviewing their new Webflow build? Give them a report button instead of a Loom-and-email chain: annotated screenshots, console errors, and failed requests, filed straight into your Jira.

Start FreeSee the install

Why Webflow teams use it

Client feedback arrives as vague emails

"The menu looks off on my laptop" becomes a Jira issue with a screenshot of exactly what they saw, plus browser and viewport data.

No-code site, but the bugs are technical

Webflow interactions and embeds still throw console errors. Reports carry them automatically — no asking clients to open DevTools.

Designer-perfect styling stays perfect

The widget renders in Shadow DOM, so it cannot inherit or disturb your Webflow classes.

Install on Webflow in minutes

No SDK, no backend changes — the widget is a single ES module.

  1. 1

    Project Settings → Custom Code

    Paste the snippet into the site-wide head/footer code (or per-page custom code for staging-only rollout). This uses Webflow’s standard custom-code feature — no app install.

  2. 2

    Publish the site

    The widget button appears immediately after publish.

  3. 3

    Connect Jira

    OAuth once; client feedback lands as ready-to-work issues.

<script type="module">
  import IssueCapture from 'https://issuecapture.com/widget.js';
  IssueCapture.init({ apiKey: 'ic_your_key' });
</script>

Works on all Webflow plans that allow custom code.

Every report arrives in Jira with

Annotated screenshot

Reporters circle the problem instead of describing it

Console errors

JavaScript errors and warnings from page load onward

Failed requests

4xx/5xx network calls, with privacy filters

Browser context

URL, browser, OS, viewport — automatically

Then AI triage sets priority and category and links duplicates — before the issue lands in your project (team-managed and JSM included).

Webflow bug reporting: FAQ

Do I need a Webflow app or plugin?›

No — there isn’t one and you don’t need one. The widget is a single script tag pasted into Webflow’s Custom Code settings, which is available on paid site plans.

Can I enable it only on the staging domain?›

Yes — use per-page custom code, or gate the init on location.hostname so it only runs on your .webflow.io staging domain during review rounds.

Will clients need accounts to report?›

No login of any kind — they click the button, annotate the screenshot, and submit. You control where reports go in Jira.

Does it slow the site down?›

The core is ~40KB gzipped, loaded as a deferred module that never blocks rendering; the annotation editor lazy-loads only when someone uses it.

Ship the widget on your Webflow site today

Free plan with 10 issues/month, no credit card. Jira connection takes one OAuth click.

Start FreeRead the Docs
  • Works with Jira Cloud + JSM
  • Team-managed projects supported
  • ~40KB core, lazy-loaded extras