Tutorials

Step-by-step. Sanity-checked. No surprises.

Every webQsee tutorial walks you through one concrete setup, with a verifiable sanity check at the end of each step so you always know whether you're still on track. If a check fails, jump to the in-tutorial troubleshooting block.

Available now in the browser, and in the extension this autumn.

The AI analysis, the three webQsee AI strengths, Deep Inspection and the new plans are live today in webQsee web at view.webqsee.com: open a recording there, analyse it, and buy a plan or a booster if you want one. The Chrome and Edge extensions are in review and follow this autumn. Your recordings, your gallery and your account are the same in both, so nothing you do now has to be done again.

AI analysis

Ask a recording what went wrong.

Every finding cites the analyzer rows it rests on, so you can check it rather than believe it.

Start here, an overview

What it reads, the two ways to run it, what leaves your machine, and where the answer is kept.

≈ 10 min Start

Quick analysis

One API call from the browser. Connect a model, ask well, and read the coverage box that says what was left out.

≈ 15 min Start

Install the helper

One file that carries its own runtime. Needed for Deep Inspection, not for the quick analysis.

≈ 10 min Start

Deep Inspection

An agent on your own machine with the whole recording, and with your source code if you map it.

≈ 25 min Start

Compare two recordings

Record it working and record it failing, then ask what is different. With the caveats that matter.

≈ 20 min Start

Use your own agent

≈ 20 min Start

What it sends, and where

Per variant: what leaves the machine, what masking does and deliberately does not do, and what a public link shows.

≈ 10 min Start

What it costs

BYO AI or webQsee AI: the allowance on each plan, what counts as one analysis, what never counts, and the five boosters.

≈ 6 min Start

Amazon S3 cloud storage

Connect Amazon S3 to your Cloud Gallery.

Bring your own AWS bucket. webQsee never stores the payload, only the metadata.

Simplified S3 integration

One shared IAM user for the whole team. Fastest path; recommended for solo users and tiny trusted teams.

≈ 15 min Start

Multi-user S3 integration

One IAM user per team member, per-user prefixes enforced at the IAM layer. Recommended for any serious team.

≈ 25 min Start

Migrate simplified → multi-user

You started small and outgrew the shared IAM user. Switch without data migration; bucket layout stays the same.

≈ 10 min Start

One bucket, multiple teams

Cheapest topology: share a bucket across webQsee teams using per-team prefixes and scoped IAM.

≈ 15 min Start

One bucket per team

Strictest isolation between teams, separate buckets, policies and IAM users. Cleanest blast radius.

≈ 20 min Start

Self-hosted min.io

The same S3 API, your own hardware. Bucket, policy, access key, webQsee connection, and team-invite walkthrough.

≈ 25 min Start

Team management

Run more than one team out of webQsee.

Create multiple webQsee teams

How to run several paid teams under your control, and manage them centrally with one super-admin account.

≈ 10 min Start

Event classification rules

Author and share rules that flag known issues across the team. Tutorial coming soon.

Tutorial not written yet

Local Gallery hygiene

Keeping IndexedDB under control: what to prune, what to archive, what to push to the cloud. Tutorial coming soon.

Tutorial not written yet

Need a tutorial we don't have yet?

Tell us what you're trying to set up, we write tutorials in the order people actually ask for them.

Request a tutorial

Stop guessing. Start webQseeing.

Add webQsee to Chrome or Edge in one click. Recording and replay are free, no signup needed. Upgrade when you need AI analyses, cloud sharing, S3 storage and Pro-grade tooling.

Open captures without installing See pricing

Works in Chrome 103+, Edge 103+ and most Chromium-based browsers. Install instructions.