GlitchPin – Visual Bug Feedback
Collect private bug reports, screenshots, and page context directly on your WordPress website. No external service required.
Solid choice
GlitchPin – Visual Bug Feedback is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 3 weeks ago, and scores 64/100 on our health check.
- Actively developed — last update 3 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
- Needs PHP 8.3 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where GlitchPin stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| bug reports | >100 |
| feedback | >100 |
| screenshots | >100 |
| testing | >100 |
About GlitchPin – Visual Bug Feedback
From the official readme · v1.2.27Description
GlitchPin helps visitors and testers report problems without leaving the page. Administrators review reports in the WordPress dashboard.
- Floating icon-only bug button with configurable position and color.
- PluginPeer QA feedback panel: one message and Save feedback, without a second form.
- Capture the visible page, then add a message, select an area, draw, and place numbered markers with notes.
- Retry capture or upload PNG, JPEG, or WebP if automatic capture fails; annotated images are stored privately in the database.
- PluginPeer-styled report list, category/status filters, date sorting, pagination, and bulk actions.
- Five statuses: New, Confirmed, In Progress, Resolved, and Rejected.
- Optional administrator email notifications.
- Per-visitor and site-wide limits, storage quotas, and daily retention cleanup.
- WordPress personal data export/erasure support.
The widget is disabled by default. After activation, open GlitchPin > Settings, enable reporting, and choose who can submit. The default audience is logged-in users. Public visibility of the widget never grants public access to reports or screenshots.
Privacy
Reports remain in this website’s database. No data is sent to PluginPeer and no external JavaScript, fonts, or CDN resources are loaded. Optional notification email uses WordPress wp_mail and the site’s configured mail service. Messages contain the report title, category, date, and private admin link; no image is attached.
Reports contain the feedback message, numbered marker notes, annotated screenshot, page address without query parameters or fragments, and account ID for signed-in reporters. The report title is derived from the first message line. The widget does not ask for email, reproduction steps, DOM element selection, or extended diagnostics. Clicking the bug icon captures the visible page locally. Capture hides form fields, editable content, embedded frames/video, and sections marked data-ppbh-private. Other visible page content may contain personal information. Manual uploads are not automatically redacted. Review the captured image before saving; close the panel without saving if it contains information you do not want to share. Only Save feedback sends the final annotated image and message. DOM markup, cookies, tokens, and network requests are not collected as report data. Older reports and compatible API clients can contain optional email, element geometry, and diagnostics.
Original screenshots are decoded and re-encoded to strip image metadata and appended content. Only the resulting image is retained, outside the Media Library and public uploads filesystem. A capability-checked, nonce-protected administrator endpoint serves images with no-store headers. Images are PNG or JPEG after normalization; WebP inputs are converted to PNG.
Rate limiting stores a keyed hash of an IP address or account ID in an hourly bucket. Raw IP addresses are not stored. Buckets expire after at most two hours and are removed by daily cleanup. Hosting access logs are outside this plugin’s control.
Reports expire after 90 days by default. Choose another period or 0 to retain reports until deletion. Daily WP-Cron cleanup handles up to 200 expired reports per run; low-traffic sites should configure a real cron runner if timely deletion is required. Deleting a report also deletes its image. Deactivation preserves reports. Uninstall removes data only if the administrator enabled that setting first.
Use Settings > Privacy to configure your policy page and review the suggested policy text. Tools > Export Personal Data and Erase Personal Data handle reports matched by submitted email or account email. Screenshot data is included as MIME/base64 text in authorized privacy exports. Reports without either identifier must be handled manually by an administrator.
Development
TypeScript sources are included under src/. Run npm ci and npm run build to rebuild public/assets/reporter.js. No build step or Node.js is required on the production WordPress site. See docs/TECHNICAL.md for architecture, API contracts, testing, and release checks.
Installation
- Upload the plugin folder to wp-content/plugins or install the ZIP from Plugins > Add New.
- Activate GlitchPin.
- Open GlitchPin > Settings and check Enable bug reporting.
- Choose the reporting audience and save settings.
- Open a frontend page as an eligible visitor and click the bug icon (Report a bug).
- Add a message in the PluginPeer feedback panel. Optionally select an area, draw, or add marker notes, then choose Save feedback. There is no second form.
PHP GD is required for saving screenshot feedback. Supports MySQL/MariaDB with InnoDB and WordPress Playground with the WordPress SQLite Database Integration adapter. Multisite administrators should activate the plugin separately for each site; network-wide activation is intentionally refused.
Changelog
The bug icon always captures the visible page and opens the feedback panel. Save feedback submits directly. Existing reports and audience restrictions are preserved.
1.2.27
- Keep scrolled captures aligned with the visible page, including pages that use smooth scrolling.
- Preserve image layout outside the viewport so failed capture-frame reloads cannot shift visible content.
- Retain independent display sizes when the same image appears multiple times.
1.2.26
- Preserve visible page images in feedback captures when WordPress Playground cannot reload them in the capture frame.
- Keep responsive and lazy-loaded image pixels in saved feedback without changing the live page or private-section masking.
- Capture external images that permit anonymous CORS access while keeping screenshots safe to export.
1.2.25
- Keep the page visible through a transparent background while preparing a screenshot, with a compact capture panel on mobile.
- Allow capture cancellation and ignore results from cancelled attempts.
1.2.24
- Remove deprecated GD image cleanup calls to prevent PHP 8.5 warnings when processing screenshots.
1.2.23
- Preserve loaded page styles when capturing feedback in WordPress Playground.
- Keep stylesheet order, imported rules, media conditions, and relative asset URLs in captured screenshots.
1.2.12
- Fix feedback storage in WordPress Playground with SQLite using transactional row locking instead of MySQL advisory locks.
- Keep report and screenshot deletion atomic with portable queries and checked transaction results.
- Add a retryable schema upgrade that preserves existing feedback and screenshots.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best GlitchPin alternatives
All bug reports plugins →| Rank | Plugin | Active installs |
|---|---|---|
| 1 |
|
<10 |
FAQ
GlitchPin – Visual Bug Feedback: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is GlitchPin – Visual Bug Feedback free?
Yes. GlitchPin – Visual Bug Feedback is free to download and use from the official WordPress.org plugin directory.
Is GlitchPin – Visual Bug Feedback safe to use in 2026?
GlitchPin – Visual Bug Feedback is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 3 weeks ago, and scores 64/100 on our health check.
How many websites use GlitchPin – Visual Bug Feedback?
GlitchPin – Visual Bug Feedback is active on <10 WordPress websites and has been downloaded 342 times since it launched in October 2026. It was downloaded 341 times in the last 30 days.
Does GlitchPin – Visual Bug Feedback work with WordPress 7.1?
Yes. The developer has tested GlitchPin – Visual Bug Feedback up to WordPress 7.1.5, the latest release. It requires WordPress 6.4 or newer.
What PHP version does GlitchPin – Visual Bug Feedback need?
GlitchPin – Visual Bug Feedback requires PHP 8.3 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was GlitchPin – Visual Bug Feedback last updated?
The latest version, 1.2.27, was released on November 2, 2026 (3 weeks ago).
Who makes GlitchPin – Visual Bug Feedback?
GlitchPin – Visual Bug Feedback is developed and maintained by PluginPeer.
What are the best alternatives to GlitchPin – Visual Bug Feedback?
The most popular alternatives to GlitchPin – Visual Bug Feedback are FeedHub – Feedback Widget (<10 installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card
