Help / 07
Troubleshooting
When a site fights back
A site won't capture properly
The escalation ladder, in order:
- Use the canvas like a browser. It is one. Log in, click through consent walls and bot checks, dismiss overlays, and use Tidy for banner clutter — then capture.
- For recording, switch to Hands-on and drive the page yourself. Sites that misbehave under automation usually behave for a human.
- All else fails: Import. Screenshot the site by any means and ⌘I it in. Everything downstream — Compose, Mockup, export — works identically on imports.
Password-protected staging sites
Sites behind a server-level password wall (HTTP basic auth, the usual staging protection) show a sign-in sheet when the page loads. Credentials go to that site only and last for the session, so a multi-viewport run signs in once. Regular on-page login forms need nothing special — sign in on the page like any browser.
Video frame rates
30fps at typical sizes — 1080p records with plenty of headroom. At very large viewports (4K and up) WebKit's snapshot path becomes the bottleneck and recordings land around 25–27fps. Every frame is timestamped against the wall clock, so duration and pacing stay exactly right; you just get fewer frames per second at those sizes.
Requirements
macOS 14 Sonoma or later, Apple Silicon or Intel. No Windows or Linux version — Plures is built on WKWebView and the system capture pipelines, and porting would mean a worse product everywhere. ShareX for stills and OBS for video are the good options over there.
Updates
Plures checks for updates with Sparkle and installs them in-app (Plures menu > Check for Updates). Updates to Plures 1 are free. Installing them is optional.
Report a problem
Help > Report a Problem gathers the app version, macOS version, and any Plures crash logs into a pre-filled email draft. Everything the email will contain is visible before you send it.
Still stuck? support@plures.app.