-
Temporarily logged out.Reload webQsee to re-verify your account.
-
Happy with webQsee?
-
Send feedback
-
Reload window
Capture live HTTP, console, WebSocket and SSE traffic, replay a saved report, or open a previous capture from your gallery.
Pick a webQsee storage in the region of your choice and you are done in one click. Or bring your own Amazon S3 or S3-compatible bucket, in which case captures and recordings stay entirely on your storage. Either way, only non-critical metadata (title, capture date) lives on webQsee servers.
Your team already has a cloud storage (cloud storage), but this machine cannot connect to it yet. Personal S3 credentials are stored locally per machine and never leave it, so they have to be entered once on every browser you use.
Website screenshot + debug data: network and console events plus a tab screenshot and (optionally) cookies. Re-importable into webQsee by anyone for free. Comparison to HAR
Detailed HTTP Archive. Contains only HTTP events.
Simple overview including matched rules. Contains events of any type.
Single-file exports for specific data.
The Cloud Gallery requires an existing Amazon S3 storage or an S3 compatible storage (like min.io). We decided to go with a bring-your-own-storage approach, because data you capture with webQsee is none of our business. The webQsee browser extension connects to your configured S3 compatible storage directly via browser.
Captured videos, screenshots, http traffic therefore never land on webQsee servers, but on your own storage. Only non-critical metadata like title or capture date will be stored on webQsee servers.
Take a look at our documentation for the Cloud Gallery and the Cloud Storage, if you want to know more. We provide tutorials for the correct setup of Amazon S3 and third-party S3-compatible storages. A correct setup includes bucket policies that enforce correct user permissions for the data stored in S3.
Saved locally on this machine only. webQsee never transmits these to any server.
Settable by super-admins. These values are shared across the whole team.
S3 connection options forwarded to the AWS SDK for JavaScript v3. Do not include credentials here.