A browser recorder that saves a video and serves a share page is a day's work: getDisplayMedia, MediaRecorder, an upload route and ffmpeg for an MP4. The weekend goes on what makes Loom dependable: uploading while you record so the link is ready the moment you stop, surviving a dropped connection, fast playback for viewers far away, and system audio, which only some browsers can capture. Comments, shared workspaces and the AI titles and chapters stay with Loom, and so does the bandwidth bill if many people watch.
Before you buildLoom Starter gives 25 videos of up to 5 minutes at 720p. If your clips are short and few, you may not need to pay or build.
Build me a personal screen-recording and sharing tool to replace Loom. Requirements: - Node.js 22 + TypeScript: a Fastify server and a React page built with Vite. `npm start` serves http://localhost:4600; recording needs a Chromium-based browser. - Recorder page: getDisplayMedia for the screen (with system audio where the browser allows it), getUserMedia for the microphone, and an optional draggable camera bubble drawn on a canvas. MediaRecorder writes video/webm (vp9, opus). Controls: 3-second countdown, pause, resume, stop. - Upload while recording: send each 5-second chunk to POST /api/videos/:id/chunks so the share link is ready seconds after stop. If the network drops, queue chunks in IndexedDB and resume. - Storage: ./data/videos/<id>/ for files and better-sqlite3 (./data/videos.db) for title, created, duration, size, visibility and view count. After stop, ffmpeg makes an H.264/AAC MP4 and a poster image; the original webm is kept. - Share page /v/<id>: HTML5 player, title, Open Graph tags and a view counter that skips my own views. Visibility is unlisted by default (a random 12-character id) or password protected. - /admin behind one password from .env: list, rename, trim start and end with ffmpeg, download MP4, delete with confirmation, free disk space. - Optional transcript: run whisper.cpp when WHISPER_BIN is set in .env; otherwise skip it. - Single user. No accounts, no telemetry, local-first: files stay on this disk. - Out of scope: comments, teams, mobile apps, a native recorder, editing beyond trim, AI summaries. - README: installing ffmpeg, exposing /v/ through a tunnel or a VPS with HTTPS, and a warning that browsers can throttle a long recording in a background tab.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Loom.
Change the storage in the recording tool in this folder. Requirements: - Add a storage interface with a local-disk implementation and an S3-compatible one (the AWS SDK v3), chosen by STORAGE=local|s3 and S3_* variables in .env. - Upload the MP4 and poster to the bucket after processing; the share page uses signed URLs that expire after 6 hours and supports byte-range requests. - Provide `migrate-storage` that copies existing videos, verifies sizes and leaves the local copy until I pass --delete-local. - Update the README, including bucket permissions.
Add comments to the share pages of the recording tool in this folder. Requirements: - A viewer enters a name and a message; the comment stores the current playback time and shows as a clickable timestamp that seeks the player. - Rate-limit per IP without storing the IP, add a honeypot field, and escape every comment. - I can delete any comment from /admin and turn comments off per video. - Send me an email through SMTP settings in .env when a comment arrives. - Update the README.
Add embedding to the recording tool in this folder. Requirements: - /embed/<id> serves a minimal player page that can be framed; set frame headers only for unlisted and public videos, never for password-protected ones. - /oembed?url=... returns oEmbed JSON, and the share page advertises it with a link tag. - Respect the visibility setting and the view counter. - Update the README with a copyable iframe snippet.
Add chapters to the recording tool in this folder. Requirements: - When a transcript exists, send it to the Anthropic API (ANTHROPIC_API_KEY in .env) and ask for 3 to 8 chapters as JSON with a start time in seconds and a title of at most 6 words. - Validate times against the video duration and store the chapters; show them under the player and in the admin list, editable by hand. - Skip silently when there is no key or no transcript, and show what each run cost in tokens. - Update the README.
Loom is a habit with a ready audience: viewers open a link and it plays, with no account or install. Teams pay for the library, comments and view data around the recording, and for not having to host and back up video themselves.
Estimate · Local use costs nothing. To share links you need a tunnel or a small VPS, and video storage and bandwidth grow with what you record. The build is token usage on your agent plan.
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Starter | $0/user | $0/user | Up to 50 members, 25 videos per person, 5 minutes per recording, 720p, unlimited screenshots, transcriptions in 50-plus languages. |
| Business | $18/user | — | Unlimited videos and length, up to 4K, custom branding, password-protected videos, engagement insights you can export, 3 extra spaces, downloads. |
| Business + AI | $24/user | — | Business plus AI titles, summaries, chapters and tasks, edit by transcript, filler-word and silence removal, automatic meeting notes. |
| Enterprise | custom | — | SSO and SCIM, a 99.95% uptime SLA, activity logs, retention policies, download restrictions, a dedicated account manager. |
Starter allows 25 videos per person of up to 5 minutes each, at up to 720p.
Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Comments, emoji reactions and shared spaces for a team, AI titles, summaries, chapters and transcripts in 50-plus languages.
About $18 a month on the Business plan per seat, $216 a year (checked 2026-10-14).
Comments, emoji reactions and shared spaces for a team; AI titles, summaries, chapters and transcripts in 50-plus languages; Video delivery from Loom's infrastructure to viewers anywhere; The desktop and mobile recorders; Engagement insights with per-viewer data. If any of those matter to you, keep paying.
Yes: Cap (open source), Screenity (open source), OBS Studio (open source).