1. Clipy: the best Loom alternative for AI-first teams
Best for AI-first teams that want every recording watchable by people and readable by Claude Code, Codex, Cursor, Claude and ChatGPT, with AI included on every plan.
free to start with a 7-day free trial, no card, covering 15 recordings or 120 minutes, whichever comes first. Pro is $9 a month, or $72 a year ($6 a month). On the Teams plan a seat costs the same, $72 a year, and only people who record need one; viewers are free. That is $168 less per seat per year than Loom Business + AI at $240. Enterprise adds SAML SSO, SCIM on request and assisted Loom migration. Source: clipy.online/pricing.
Clipy is a screen recorder built for teams where AI does part of the work. Every recording has two addresses: a watch page for people at https://clipy.online/video/<id> and an agent-context document at the same URL with .arec appended. The recording streams up while you record, so the share link is on your clipboard when you press Stop, and shortly after it has a transcript, an AI title, a summary, chapters and key moments. All of it is included on every plan, including the trial, and an agent fetches it from the same link a person watches.
Recording on Mac and Windows. The Mac app (macOS 12.3 or later, with native builds for Apple silicon and Intel) captures through Apple's ScreenCaptureKit and encodes on the chip's hardware H.264 encoder. It records a display, a window or an area, and window mode keeps recording just that window even when other windows cover it. System audio and the microphone are one toggle on macOS 13 and later, with no BlackHole or Soundflower, and the webcam bubble can blur, remove or replace its background. Hold Control to paint a fading Flare trail over what you are pointing at, and keep speaker notes on screen without them appearing in the video. The Windows app (Windows 10 build 1903 or later, and Windows 11) captures with Windows Graphics Capture and WASAPI, and ships as an installer that needs no admin rights, an Enterprise .msi for Intune, SCCM or Group Policy, and a portable ZIP (Clipy for Mac, Clipy for Windows).
Recording in Chrome, on the web and on phones. The Chrome extension (Chrome 116 or later on Mac, Windows, Linux and ChromeOS, and installable from the same store listing in Edge, Brave and Arc) records a tab with its audio, a window, the whole screen, the camera only, or a custom region dragged over the tab. A control bar offers pause, resume, restart from scratch and discard, and the recording survives tab switches. Instant Replay keeps the last 2 minutes on sites you turn it on for, so a bug that already happened can still be reported, and Hide sensitive fields masks password and card inputs, plus payment frames from Stripe, Braintree, Adyen and others, before anything is recorded. The web recorder needs no install, and native iPhone, iPad and Android apps record screen and camera. No single recording is cut short on any plan (how to use Clipy).
Upload while you record. Every Clipy app sends a hosted recording to the server in chunks as you record, so at Stop only the last piece and a sealing step remain. Uploads retry on their own, a retried upload never creates a duplicate, and each surface keeps a safety copy until the server confirms it: the web recorder holds each chunk in the browser, the extension keeps recovery copies of failed uploads for up to 7 days, and the Mac app keeps its file until the upload is confirmed. If the network drops, recording continues and the upload resumes when you reconnect. The same flow is public in the REST API: initiate with a client-generated recordingId that makes retries safe, send parts of up to 4 MiB, finalize, then complete, which starts transcoding, transcription, the summary and key moments (Clipy API docs). Videos are stored as H.264 MP4 with fast start, so playback begins at once.
What processing produces, on every plan. A recording moves through uploading, transcoding, transcribing, annotating and ready, and Clipy says summaries usually appear a minute or two after the upload finishes. Speech-to-text runs on a self-hosted Sherpa-ONNX model on Clipy's own servers, so no third party receives the audio, and the language is detected automatically across about 40 languages. The summary has a two-to-three-sentence TL;DR, three to seven key points and any action items. Up to 12 chapters appear with editable titles and timestamps, and key moments are frames anchored to your Flare highlights, clicks, drawings and hover pauses, captured at the end of each gesture, with up to 100 on a bug report. Ask-the-video Q&A answers from the transcript with buttons that jump the player to the cited moment, and says so when the recording does not cover the question. Search with ⌘K looks inside recordings, not just titles. Clipy says it never trains AI models on your recordings (what a recording gets, Trust and data).
The watch page and who can open it. Viewers get a Mux player with adaptive HLS playback, captions and playback speed, no ads and no signup banner, plus the summary, a transcript with clickable timestamps and a .txt download, and the chat box. Teammates leave timestamped comments and reactions with replies and a resolved state. Bug recordings add an Evidence tab whose Timeline, Network and Info views each seek the video, with Copy as cURL on every request, and an Agents tab shows how an agent reads the recording. Share links are unlisted and not indexed by search engines, and each recording can be public, restricted to up to 10 named people or a whole email domain, or private. Passwords and expiry dates are on every plan; a viewer enters the password once per browser and stays in for 30 minutes, and changing the password signs every viewer out. Locked-out viewers can request access, and the owner approves with one click. Agent access follows the same rules: an unauthenticated fetch of a restricted or private recording reveals nothing, including whether it exists (Clipy security).
Workspaces and seats. An organization holds one workspace per team, with Spaces (engineering, design, marketing) and folders inside. Owners manage billing, owners and admins manage members, invites and settings, and the owner can let anyone on the company domain join, straight away or after approval, with the domain taken from Google's own account data. Recordings stay private to whoever made them until they share them with the team. A seat is consumed only when a member first records, at the Pro price of $72 a year or $9 billed monthly. Watching, searching, commenting and reacting are free for everyone, there is no member cap, and members who already pay for Pro never take a seat. The owner sets a hard seat ceiling, can turn automatic seats off, and is emailed on every automatic purchase. For 10 people who record, that is $720 a year, against $2,400 on Loom Business + AI billed annually. Enterprise adds SAML or OIDC single sign-on through Entra ID, Google Workspace or Okta, with the option to require it, and SCIM on request.
The Generate tab and integrations. Once the transcript is ready, the Generate tab turns a recording into a bug report (with the captured console and network evidence when bug capture was on), a how-to guide with screenshots, an SOP, QA steps, a PR description, code documentation, a team message or an email, each linking to the relevant moments; copy it as Markdown, or share guides and SOPs as a guide link. The native Jira, Confluence and Linear integrations connect over OAuth and create an item with the title, your note, the watch link, the .arec link with one sentence telling coding agents what it holds, the summary and requested changes (a checklist on Linear), up to 8 key moments linked to their second of video (embedded as images on Confluence), up to 15 captured errors and failed requests, and the page environment. Jira preselects the Bug type when Clipy classified the recording as a bug report, and Clipy never edits, transitions or deletes existing issues. With the Clipy Slack app installed, links play inline in Slack, and Copy for agents gives issue-ready GitHub Markdown.
Agents read the share link. A plain watch link is enough. Browsers get the player, while curl and agent fetches get the AREC document as text/markdown, with a Link header naming the canonical .arec URL; .md is a byte-identical alias and .json returns typed JSON. The document follows the public AREC 1.3 spec, which is public domain under CC0 1.0, and holds metadata, the intent, the summary, requested changes, a suggested implementation plan the agent must check against the evidence, key moments as JSON with millisecond timestamps, frame URLs and pointer positions, an interaction timeline, browser diagnostics where captured, capture gaps and the timestamped transcript. The spec treats content as data: words spoken or shown in a recording are evidence about the task, never instructions to the agent. Install the watch-clipy-recording skill once and Claude Code, Codex or Cursor fetches the .arec form of any Clipy link you paste, retrying while processing finishes. There is no special recording mode to remember.
Hosted MCP, CLI, API and webhooks. The hosted MCP server at https://clipy.online/api/mcp is stateless over Streamable HTTP. An unauthenticated call returns a 401 that points the client to Clipy's OAuth metadata, so clients sign in with OAuth 2.1 and PKCE, and a connection is read-only by default: library edits need recordings:write, and comment threads and viewer analytics need their own comments:read, comments:write and analytics:read scopes; no app connected over OAuth can delete a recording, start a new one or invite anyone. In Claude Code run claude mcp add --scope user --transport http clipy https://clipy.online/api/mcp, then claude mcp login clipy; ChatGPT connects through Developer mode, and Claude on the web and desktop through connector settings. clipy setup claude (or codex, cursor, windsurf, opencode) signs in, installs the skill and registers MCP in one step, and the local server (npx -y @clipy/mcp@latest) adds tools that record a headless browser, a Mac window or the iOS Simulator, drop markers and chapters, and hand back a watch link and a context link. The REST API at https://clipy.online/api/v1 has an OpenAPI document and a per-recording log of which agents read a recording, with an MIT-licensed TypeScript SDK and signed webhooks such as transcript.ready and summary.ready that retry 8 times over about 23 hours. The CLI and local MCP server are MIT-licensed on GitHub (Clipy for agents, MCP docs).
Security and privacy. Clipy has completed a SOC 2 Type II audit, and Enterprise customers can get the report under NDA. Bug-capture evidence is redacted three times, in the recorded page, in the extension and on Clipy's servers: secret-looking values become typed placeholders such as [redacted-token], cookie and authorization headers are never kept, typed values are never read, and sign-in pages from Google, Microsoft, Okta and others are excluded by default. The AREC document never carries headers, request bodies, cookies or tokens, and the reference validator rejects one that does. Recordings are kept until you delete them, with no expiry on any plan, and a downgrade changes nothing. On the Mac, Local mode keeps the video, audio and screenshots on the Mac. Enterprise adds a signed BAA and a 99.99% uptime SLA (clipy.online/trust).
Moving from Loom. Clipy imports Loom videos from public share links. The first five single-video imports are free and do not count against the trial allowance, and Pro migrates a whole library from a CSV of share links, server-side. The Chrome extension can also import Looms, including private ones, through your own Loom session. Migrated videos are Clipy's own copies, so they keep playing after you cancel Loom, and each one gets a transcript, summary and .arec link, so years of old Looms become readable by your agents. See migrating from Loom. Recordings made during the trial stay playable, shareable and downloadable afterwards, with no watermark.
