Cap on X

Most praise is brief and practical: people answer "what should I use?" threads with Cap, say their whole team uses it, and post about recording demos with it. 5 people credit the free, open-source model, several as the reason to pick it over paid tools; one says it is "free and solid", and another that it "just WORKS" on Linux where the alternatives they tried did not.

7 people praise the rewritten version for speed, and several name the size drop from 3.7 GB to 440 MB once the embedded browser was gone — one calls that "the actual fix here". A contributor posting about a first merged contribution says it is cool to contribute to a product they actually use.

The unhappy 4 are specific rather than vague: audio and video out of sync on a Mac recording, white artifacts in the exported video, a five-minute limit on free recordings called too short, and one person who preferred the old interface. 2 people are undecided, including one who tried it on Windows, says it lagged the whole system, and might try again.

The slowness talk is unusually concrete. Contributors report imports decoding on a single CPU thread, GPU cores sitting idle during export, the cursor image re-hashed on every tick, and the editor rebuilding waveforms sixty times a second; fixes are posted with before-and-after numbers, such as export 104s → 18s, imports 62s → 33s at 1080p, and NVENC use going from 24% to 100%. A few users just say it was "janky" and they stopped, or that it lagged a whole Windows system. One asks whether rendering not loading all the cores is a bug.

The bugs 6 people name are specific: keyboard segments that turned ⌥⌘← into "⌘LOPTION", the timeline jumping back to 0:00 when a clip is added, no fullscreen preview while editing, a video stuck on "Loading video...", a transparent installer window on Windows, and a recording bar where close sits where pause should be.

3 people had audio and video out of sync, white artifacts on export, or imports landing a frame short. 2 on Linux describe configuring everything by hand because it is not compiled for Linux, and one says it "sometimes breaks".

The Loom mentions are both switches: one says they "recently switched from loom to @cap", and another reports cancelling a Loom account and signing up to Cap saved them $75 — so price is the stated reason in one of the two.

On OBS the two posts pull opposite ways: one asks outright whether Cap is better than OBS, adding that they use Arch, while the other calls OBS "bloated lately" and Cap a great choice for recording.

The two remaining names are one-offs rather than switches. One person recommends Cap and then offers CleanShot as the alternative if you want a one-time purchase instead of a subscription. Another answers a mention of Paper with "no need, we have @cap".

With 6 people in the section, nothing here adds up to a trend: these are individual mentions, many in reply threads where someone is asking what to record with.

The sponsorship questions are practical and slightly anxious: whether the offer is "still going on" now that a PR got merged, whether they can send PRs at all, whether it works for more than one merged PR, and whether accessibility fixes count when sent "a lot of them at once". One says they have 18 PRs merged and "still got nothing".

2 people ask where Cap runs and whether they can host it themselves. 2 question the 3.7 GB to 440 MB comparison — what the embedded web view was holding, and whether the old figure was measured on the same machine and video, "apples to apples".

2 ask about driving Cap from outside the app: one asks whether it has a CLI, another wants an MCP so agents can record demos. 2 ask whether it will cope with their setup — a heavy Blender scene on a 16 GB Mac, and recording on an external monitor that currently means turning off the main display. Single questions cover whether an update needs a reinstall or just a download, whether editing videos costs extra, and, from one person, what Cap is.

The filler-word requests are short and direct — "automatic filler word removal", "Filler words removal for sure" — and one comes with a reason: a first recording in a long time was "perfect except for this".

The contributor asks are about throughput as much as features: people want to know when the team is "ready to triage and accept PRs", and one asks specifically about a merged PR and another still awaiting review. One person repeatedly asks for sharing to be set once rather than per person and per video: domain-based access, org-level defaults, and default permissions for new videos. Better transcripts mean speaker diarization, grouped utterances, a choice of transcription model and transcript editing.

Single wishes cover expirations on caps (3, 7 or 15 days, so they delete themselves), an audio loop, voice narration, a SwiftUI migration, more incremental releases "instead of waiting for a month", caption rendering for Chinese, Japanese, Arabic and Hindi, connecting an AI model to generate versions, and more apps written in Rust.