Record a video
Privacy first: your video is recorded in this browser and stored on this device only. It never leaves your device unless YOU choose “Upload to my Drive”. Toolzo stores no video file anywhere.
Your browser will ask permission to share your screen (and camera/mic). Recording needs a secure page (https or localhost) — this preview is https, so it works. On a phone, screen recording may not be offered by the browser; camera-only recording works on most phones.
Recording… 0:00
Preview your recording
Trim is a playback marker: the player starts at trim start and stops at trim end. v1 does not re-encode the file, so a downloaded file is still the full recording — the trim applies in the Toolzo player and in the shared view. A physically trimmed download is a before-selling item.
How it works
- Record — screen, camera and mic in the browser (MediaRecorder). Nothing is uploaded while you record.
- Trim — set a start/end marker; the player honours it.
- Share — upload the file to YOUR OWN Google Drive (Pricing & settings → Connect Google Drive), then copy the Drive share link. The video lives in your Drive, not on Toolzo's servers.
- Measure — when someone watches through the Toolzo player, play / pause / seek / watch-time is logged (demo: this browser; live: Worker + D1). Google Drive itself reports no per-viewer watch time — that is why the player exists.
Demo mode: recordings are stored in this browser (IndexedDB). Your library starts empty — record a video to see it here.
Storage
Videos are stored in this browser (IndexedDB). Browsers limit how much a site may store — export old recordings to your Drive or download them as .webm files, then delete them here to free space. Estimated size at the default ~2.5 Mbps bitrate: 1 minute ≈ 19 MB, 10 minutes ≈ 188 MB.
Player
Share from your own Drive
Local-only means a Toolzo link cannot play the video for anyone else — the file is on your device. So sharing works through YOUR Google Drive: upload the recording to your Drive, then share the Drive link. The video stays yours, in your Drive, under your privacy settings. Toolzo never sees the file.
Watch it back (shared view)
Open this page with ?watch=<drive-file-id> and the player below loads the Drive file (it must be shared “Anyone with the link” in Drive). Analytics on that view are logged to the Worker when live, or kept in this browser in demo mode.
Per video
Views = distinct sessions that pressed play. Watch time = the longest watched-seconds recorded per session (a viewer who re-watches counts once, at their longest watch). Completion = sessions that reached the end. In demo mode the numbers come from this browser only; in live mode the Worker (D1) counts them across every viewer.
Top video
Pricing — $999/year · 15 users
Toolzo Loom — $999/year, 15 users included.
That is $66.60 per user per year (≈ $5.55 per user per month) — plain arithmetic on $999 ÷ 15, not a separate price. No monthly price was set; the only confirmed price is $999/year for 15 users. Loom's own prices for comparison: Business $15/user/month, Business + AI $20/user/month — 10 users on Business = $1,800/year. Payment checkout (Paddle) is not built yet — no payment or licence gate in this preview.
Cost to Toolzo: $0/month at start — videos live on the user's device / their own Drive, so Toolzo pays no video storage. The simple HTML5 player needs no backend at all; analytics needs only the light Workers + D1 backend (free tier: 100,000 requests/day, 5M rows read/day; Workers Paid $5/month after the free tier).
Connect Google Drive
Create it once in Google Cloud Console → APIs & Services → Credentials → Create OAuth client ID (Web application), enable the Google Drive API, and add this page's origin (e.g. https://toolzo.pages.dev) as an authorised JavaScript origin. Toolzo has no Drive key of its own — nobody will hand over API keys, so the user connects THEIR OWN Google account. The client ID and access token stay in this browser in demo mode.
Backend — live analytics
Leave blank for demo mode (analytics stay in this browser). Paste the deployed Worker URL for live mode — see README “Deploy the Worker”. The Worker is not deployed yet. Live mode stores video metadata and player events in D1 and serves the analytics dashboard across viewers. The video files themselves are NEVER sent to the Worker — only metadata and play/pause/seek/watch-time numbers.
Data
About
Toolzo Loom is clean-room code written for Toolzo — own UI, own name, own backend. Loom was used only as a feature checklist (screen + camera + mic recording, trim, share, HTML5 player, watch analytics); no Loom code, UI, wording or branding was copied. There is no good open-source Loom clone to fork — the recorder is the browser's own MediaRecorder API and the player is plain HTML5 video. Full notes in THIRD-PARTY-LICENSES.md.
Honest limits: screen recording needs a desktop browser (Chrome/Edge/Firefox) — most phone browsers do not offer screen capture, camera-only works on phones. Trim is a playback marker in v1, not a re-encoded file. Drive upload needs the user's own Google OAuth client ID and the Drive file shared “Anyone with the link” for others to watch it. Analytics count only views through the Toolzo player — Drive's own view count is separate and has no watch time.