Recordly

Recordly is a desktop screen recorder and editor built for creators who need polished demo videos, product walkthroughs, and tutorials without sending raw footage to a motion designer. It combines native screen and window capture with an in-app editor so the entire workflow — record, trim, zoom, style, export — happens in one free, open-source application for macOS, Windows, and Linux.

What sets Recordly apart from a plain screen recorder is the motion-driven presentation layer built into the editor: automatic zoom suggestions based on cursor activity, smoothed and stylized cursor rendering, a webcam bubble overlay with zoom-reactive scaling, and a styled frame around the final composition with wallpapers, gradients, padding, rounded corners, and shadows. A drag-and-drop timeline supports trims, speed regions, text/image annotations, and extra audio tracks, and work can be saved and reopened as .recordly project files.

Under the hood, Recordly leans on platform-native capture where it matters — macOS ScreenCaptureKit, a native Windows Graphics Capture helper with WASAPI audio, and Electron-based capture on Linux — plus custom native helpers for GPU-accelerated compositing and export rather than relying solely on browser-level rendering. A permission-gated extension system lets the community add cursor effects, device frames, wallpapers, and render hooks, distributed through the Recordly Marketplace.

Recordly is licensed under AGPL-3.0 and started as a fork of the OpenScreen project, with the maintainers noting over 80% of the code has since diverged. It is under active development with frequent releases and accepts community pull requests, with contribution areas explicitly called out for Linux capture, export performance, UI polish, localisation, and new editor tools.

What You Get

• A cross-platform desktop recorder (macOS, Windows, Linux) using native capture backends per platform for higher-fidelity screen and window capture than generic browser-based recording.
• A full non-linear timeline editor for trims, zoom regions, speed changes, text/image/figure annotations, and extra audio tracks, with work saved as reopenable .recordly project files.
• Automatic, cursor-activity-driven zoom suggestions plus manual cursor styling controls (smoothing, motion blur, click bounce, sway, size, loop mode) so recordings read as intentionally directed rather than raw footage.
• A webcam bubble overlay with preset or custom positioning, mirroring, roundness, shadow, and optional zoom-reactive scaling for talking-head style demos.
• Frame styling for the final export — built-in and custom wallpapers, solid or gradient backgrounds, padding, rounded corners, blur, drop shadows, and aspect-ratio presets.
• MP4 and GIF export with quality, frame-rate, loop, and size controls, plus a community extension marketplace for adding cursor effects, device frames, and render hooks.

Common Use Cases

• Recording product walkthroughs and feature demos without hiring a motion designer.
• Producing developer-facing GIFs and clips for READMEs, changelogs, and pull requests.
• Sending async narrated screen updates to a remote team as a self-hosted Loom-style alternative.
• Creating styled marketing and launch videos with branded wallpapers and frames.
• Recording and lightly editing tutorial or course content with annotations and extra audio.

Under The Hood

Architecture Recordly is a multi-window Electron application with a clear split between the main process and a shared renderer bundle. The main process organizes IPC handlers by domain (export, recording, cursor, captions, project, paths) and centralizes window creation for several distinct window types — a HUD overlay, the full editor, the source selector, a countdown overlay, and an update toast — that all load the same built renderer, differentiated at runtime by a windowType query parameter read at the top of the React entry point. Platform-sensitive behavior (permission policy, navigation hardening, GPU command-line switches) is factored into small, pure, independently testable modules rather than being inlined into the main process file, and window/state wiring is passed in via callbacks rather than through global singletons. The renderer mirrors this discipline: the export pipeline lives in a large family of narrowly scoped modules (bitrate policy, frame rendering, muxing, audio routing, GIF encoding) behind a shared typed interface, so the editor, exporter, and extension host can evolve independently as long as that shared project-state contract holds. Overall this reads as a deliberately layered, modular architecture rather than an ad hoc Electron app.

Tech Stack The stack is Electron with a React renderer, written in strictly typed TypeScript and built with Vite (including a dedicated Electron/preload build pipeline). The UI layer combines Radix UI primitives, Tailwind CSS, and a timeline/drag-and-drop toolkit for the editor; scene composition and export rendering run on PixiJS with a filter pipeline. Media handling blends browser-native demuxing/muxing libraries with bundled FFmpeg binaries, and is supplemented by several custom native helpers built via platform-specific build scripts: a GPU-accelerated compositor, a native Windows Graphics Capture helper, a Windows GPU export path, and a global cursor-tracking helper — none of which are typical for an Electron app in this category. Packaging and auto-updates go through a standard Electron builder/updater toolchain, with Biome handling linting and formatting and Vitest (including property-based testing) driving the test suite.

Code Quality Testing is extensive and consistently colocated — test files sit directly beside the modules they cover across both the Electron main process and the renderer’s library code, including property-based tests for numeric export-tuning logic. Error handling favors explicit guarded early-exits and structured returns over silent catch-and-swallow, though a few failure paths only log a warning rather than surfacing to the user. Naming is descriptive and behavior-specific, TypeScript strict mode is enabled with additional unused-code and fallthrough checks, and Biome enforces a single consistent lint/format standard across the whole repository. Continuous integration runs a typecheck, lint, and the full test suite on every change, with an advisory (non-blocking) translation-parity check that surfaces known localisation debt instead of hiding it — an honest signal about a known gap rather than an oversight.

What Makes It Unique Most open-source screen recorders in this space lean entirely on browser-level capture and canvas rendering. Recordly instead invests in platform-native capture and a GPU-accelerated native compositing/export path alongside its standard renderer, aiming for capture and render quality closer to proprietary tools while remaining fully open source and cross-platform, including Linux. Its permission-gated extension system and public marketplace for community-built cursor effects, device frames, and render hooks is also a genuine differentiator versus comparable open-source alternatives, most of which are closed to third-party extensibility.

Self-Hosting

Licensing Model Recordly is licensed under AGPL-3.0. All recording, editing, and export functionality is available for free in this self-hosted/local build with no license keys, feature gates, or paid tier — the only restriction is that the “Recordly” name/branding itself cannot be reused for a derivative project, and any modified version used to power a hosted service must have its full source published under the same license.

Self-Hosting Restrictions None found. Automatic zoom, cursor styling, webcam overlay, timeline editing, frame styling, MP4/GIF export, and the extension system all ship unlocked in the open-source build — no license_check, isPro, or feature-flag gating was found in the source.

Enterprise Features Not applicable — there is no separate enterprise or paid tier. Everything lives in this single AGPL-3.0 codebase.

Cloud vs Self-Hosted Not applicable — Recordly is a desktop application with no hosted/cloud product variant. The companion Recordly Marketplace hosts community-built extensions but does not gate core app features behind an account or subscription.

License Key Required No — the app runs fully without any license key, account, or activation step.