Why is recordly.dev free?

Is Recordly really free, or will it hit you with a paywall later?

Recordly is genuinely free today: the desktop recorder has no paid plan, watermark, export limit or premium feature gate.

Recordly's own website currently describes the app as fully free and open source with “no paywalls or hidden limits.” The main repository is public under the AGPL 3.0 license, while the downloadable application includes recording, timeline editing, auto-zooms, cursor smoothing, webcam overlays, backgrounds, microphone and system audio, MP4 exports and GIF exports.

We also looked for the normal signs of a freemium product: pricing pages, license keys, usage quotas, paid export resolutions, subscription prompts or locked editing tools. There is no obvious commercial funnel behind the current Recordly product.

That puts Recordly in a different category from software where “free” really means “free until you use it seriously.” Someone can currently download Recordly, record a commercial product demo, edit it and export the finished video without paying Recordly.

What normally triggers payment?	Recordly today
Subscription	No
Watermark removal	No paid upgrade required
Higher-quality export	No paid upgrade required
Premium editing tools	No paid tier
Source-code access	Public
Donations	Optional

Why would anyone give away a Screen Studio alternative for free?

Recordly is free largely because the project was created to offer a free alternative to the polished screen-recording experience people were paying Screen Studio for.

The original positioning was unusually explicit. When Recordly appeared publicly, its creator presented it as a free, open-source alternative built around the smooth cursor movements and automatic zoom effects that had made Screen Studio popular. The GitHub description itself used the phrase “open-source alternative to Screen Studio.”

That choice makes more sense when we look at Screen Studio's pricing. Screen Studio currently charges $29 per month on its monthly plan, while its annual plan works out to $9 per month. Screen Studio had therefore already proved that people cared enough about polished product-demo videos to pay for them.

Recordly could enter that validated category without convincing people that beautiful screen recordings were useful. It only needed to give users a compelling reason to try a newcomer.

Free did exactly that. “A new screen recorder with nice cursor animations” is easy to ignore. “A free open-source Screen Studio alternative” is much easier to share.

Did Recordly get a big head start from OpenScreen?

Recordly did get a meaningful head start: it began as a fork of OpenScreen rather than as a completely new screen recorder.

OpenScreen was already an open-source Screen Studio alternative. That gave Recordly an existing desktop application, editing foundation and recording architecture to work from instead of forcing one developer to build every layer from zero.

Recordly then changed a lot. The current repository says more than 80% of the code has diverged since the fork. Among the additions and changes are a fuller cursor-rendering pipeline, native capture work for macOS and Windows, Screen Studio-style zoom behavior, cursor loops, audio features and substantial editing changes.

The repository now contains roughly 1,750 commits, so describing Recordly as a simple OpenScreen reskin would be misleading. Still, starting from an existing open-source project made the early economics much easier.

A normal software startup has to fund its starting codebase with money or founder time. Recordly inherited a useful chunk of that starting codebase from another open-source project and then contributed another large body of open-source work on top.

How much of Screen Studio does Recordly actually replace?

Recordly now covers much of the core Screen Studio-style workflow, especially for someone whose main goal is turning a raw screen capture into a polished product demo.

Recordly currently offers automatic zoom suggestions, smooth cursor movement, motion blur, click effects, timeline trims, speed changes, annotations, styled backgrounds, crop controls, webcam overlays, microphone and system audio, additional audio tracks and MP4 or GIF export.

Those features reach well beyond basic screen recording. They attack the exact editing work that makes tools such as Screen Studio attractive: removing the need to manually animate every zoom, cursor movement and frame.

Screen Studio still offers something Recordly cannot fully copy with a feature checklist. Customers pay for a commercially maintained product with a controlled release process, account infrastructure, shareable links and a company responsible for keeping the workflow reliable. Its changelog, for example, shows continued releases focused on recording, export, captions and audio reliability.

So a large part of the editing value is available for $0 in Recordly today. The gap becomes more obvious when we move from features to reliability and operations.

Capability	Recordly	Screen Studio
Automatic zooms	Yes	Yes
Cursor smoothing and effects	Yes	Yes
Timeline editing	Yes	Yes
Styled backgrounds	Yes	Yes
Webcam overlays	Yes	Yes
MP4 export	Yes	Yes
Windows and Linux support	Yes	Screen Studio remains centered on macOS
Hosted sharing	Not a core Recordly service	Yes
Price	Free	$29/month monthly, or $9/month billed yearly

How can Recordly afford thousands of users without a huge server bill?

Recordly can stay free partly because most of the expensive video work happens on the user's own computer.

The architecture described in the Recordly repository is heavily local. Screen capture happens on the machine. Editing happens in the desktop application. Recordly's renderer creates the visual composition locally, and the finished MP4 or GIF is exported locally. A .recordly project mainly stores the source-media location plus the editor state required to reopen the work.

That gives Recordly very different economics from a cloud video service.

If another 10,000 people start exporting videos in Recordly, the project does not suddenly need enough servers to render those 10,000 users' videos. Their laptops provide most of the compute and storage.

Compare that with an AI video generator or a Loom-style cloud platform. More usage there can mean more GPU inference, video storage, transcoding and bandwidth. A successful free tier can become expensive very quickly.

Recordly still has website hosting, release infrastructure, software-signing costs and plenty of human work. But its marginal infrastructure cost per heavy user can stay remarkably low, which makes unlimited free usage much less crazy than it first appears.

Did making Recordly free actually help it grow?

Free appears to have been an extremely effective growth strategy for Recordly: its GitHub repository has reached roughly 24,000 stars and 1,800 forks in only a few months.

The speed is more interesting than the absolute number. An earlier GitHub snapshot showed about 9,300 stars and 684 forks. The repository now shows roughly 24,200 stars and 1,800 forks.

That means Recordly added around 14,900 stars from that earlier base, an increase of roughly 160%. Its star count became about 2.6 times larger.

GitHub stars obviously do not equal active customers. Developers star projects they want to remember, study or simply support. Still, 24,000-plus stars is far beyond what we would expect from an obscure utility that happened to be free.

The proposition also travels well in communities: polished screen recordings, open source, three desktop operating systems and no subscription. Every person sharing Recordly as a “free Screen Studio alternative” is essentially repeating the product's acquisition pitch for it.

A paid Recordly might have earned money from its earliest users. The free version appears to have bought something more valuable during this stage: distribution.

Is the Recordly community doing work that a normal company would have to pay for?

Recordly's community is now doing a meaningful amount of work that would normally require employees or contractors.

The current GitHub repository has around 1,750 commits, while Recordly releases repeatedly credit developers other than the founder for fixes and features. Recent work has covered recording reliability, audio, exports, subtitles, Windows capture, Linux behavior, project saving, extensions, webcam previews and Electron upgrades.

One beta release, for example, bundled a long series of changes from several contributors and reported a test suite of 995 passing tests with one skip before release.

A commercial screen-recording company can use subscription revenue to hire engineers. Recordly can attract engineers because they use the product, like the idea, want a feature, find an interesting technical problem or simply want to contribute to an open-source project.

Only a tiny fraction of users need to contribute for that model to become useful. With tens of thousands of people following the repository, even a very low contributor rate can produce real engineering output.

Recordly gets something back from being free. Some users pay with code, testing, translations, bug reports and distribution rather than money.

Does Recordly make any real money from donations or add-ons?

There is currently little evidence that donations or Recordly's extension marketplace amount to a serious business.

Recordly does accept voluntary contributions, and the current repository lists about fifteen people or groups in its Hall of Supporters. Earlier versions of the project publicly acknowledged individual donations, including one $100 contribution that helped with Apple Developer costs.

Those numbers look much more like community support than SaaS revenue.

The extension marketplace also deserves attention because marketplaces often become monetization engines. Recordly extensions can add things such as cursor sounds, browser frames, wallpapers, render hooks and settings panels. Yet the current marketplace is built around publishing, downloading and extending the app rather than an obvious paid-store model.

There is no strong evidence today that Recordly is quietly giving away the desktop app to make money from marketplace transactions later.

That could change. An extension ecosystem creates obvious ways to build businesses around Recordly, including paid assets, services or hosted features. For now, though, the public product still looks like an open-source project funded around the edges rather than a software business hiding its revenue model.

Could Recordly eventually start charging users?

Recordly could charge for something later, but turning the current open-source core into an ordinary subscription product would be awkward.

AGPL 3.0 does not require software to cost $0. Recordly could sell official distributions, support, hosting, collaboration features, enterprise services or other products around the open-source application.

The more important protection for users is that the code already exists publicly under an open-source license. Recordly has also accepted work from outside contributors and accumulated around 1,800 forks.

Even if a future Recordly organization wanted a more commercial strategy, the already-released code could continue being used and forked under its existing license. Moving a contributor-heavy project toward a proprietary core can also create copyright and relicensing complications unless the project has secured the necessary rights from contributors.

Charging for exactly what people currently receive for free would also weaken Recordly's best acquisition message. At $0, users tolerate some rough edges and may even help fix them. At $9 or $19 a month, people start comparing support, reliability and polish much more aggressively with commercial products.

Paid services around Recordly are perfectly plausible. A straightforward “the same app now requires a subscription” pivot looks much less attractive.

What does keeping Recordly free actually cost?

Recordly has kept its server costs low, but software signing, releases and maintenance still create very real expenses and operational work.

The current GitHub repository has roughly 198 open issues and 97 open pull requests. Reviewing that queue alone can consume a huge amount of maintainer time. Recording software also has to deal with changing operating systems, capture APIs, audio devices, GPUs, permissions and export pipelines.

Software distribution has produced an even more concrete problem. Recordly's release documentation requires Apple credentials for signing and notarizing public macOS builds. The latest beta was published for Windows and Linux without macOS installers because those Apple notarization credentials were unavailable. The Windows installer in the same beta was unsigned and could therefore trigger Microsoft Defender SmartScreen.

These are small expenses compared with running a cloud video platform, but they are exactly the kind of boring operational details a paid software company normally handles behind the scenes.

Cost or workload	How Recordly handles it today
Video rendering	Mostly on the user's computer
Recording storage	Mostly local
Engineering	Maintainers and outside contributors
Testing	Automated tests plus community testing
Support	Mainly GitHub and community channels
macOS signing	Requires Apple credentials and developer access
Release management	Maintainer-run GitHub infrastructure

Did Recordly's founder going offline expose a real weakness?

Yes. Recordly's founder becoming unreachable exposed a serious governance problem that the open-source code alone could not solve.

Recordly's official project account recently said founder and lead developer Derall, known online as webadderall, had become unreachable. The remaining admin team said it was continuing work, but it could not access money already held in the project's original Ko-fi account.

The problem became almost comically concrete around macOS releases. The active maintainers said they needed $99 for Apple Developer enrollment so they could sign the application properly, yet they could not use the project's existing donation balance to pay for it because they lacked administrative access to the account.

Money was available. The people doing the work could not reach it.

The same problem affected credentials. Recordly's latest beta omitted macOS installers because Apple notarization credentials were unavailable.

This episode gives us a much better explanation of the trade-off behind “free” than a theoretical discussion about open source. Recordly had successfully decentralized its source code, attracting contributors and around 1,800 forks, while some critical financial accounts and release credentials remained tied to one person.

Open-source code can survive its founder disappearing. A project's bank accounts, certificates and administrative permissions do not automatically decentralize with it.

Is Recordly still actively maintained right now?

Recordly is still being worked on, although the project currently looks more fragmented than its huge GitHub audience suggests.

The canonical repository remains active enough to show around 1,750 commits, nearly 200 open issues and almost 100 open pull requests. The most recent beta also contained a substantial set of reliability fixes rather than being an empty maintenance release.

At the same time, the original project has clearly entered an unusual period. As seen above, Recordly's official account says the lead developer remains unreachable, while the remaining admins have started pushing the code forward through independent forks.

The Recordly team has specifically pointed users toward Beam, developed by ExtraBinoss, and NekoCut, developed by the-wiii-lab. Beam is positioned as a more stable continuation that incorporates Recordly's beta work, while NekoCut is taking the codebase toward more AI features.

Calling Recordly abandoned would go too far. Calling it a normal, centrally managed software product would give the wrong impression too.

Right now, Recordly looks more like an open-source project splitting into several active branches after growing faster than its governance structure.

Is free Recordly reliable enough for professional work?

Recordly is already good enough for plenty of real product demos, but someone whose job depends on every recording working perfectly should still expect more risk than with a mature commercial tool.

The GitHub tracker contains concrete examples of the remaining rough edges. One recent macOS report describes helper processes piling up during window recording until memory and CPU usage could make the machine unresponsive. Other reports across the project have covered audio, permissions, cursor behavior, exports and capture problems.

An open GitHub issue tracker is not a failure-rate database, and popular software naturally accumulates bug reports. Screen Studio's own changelog regularly contains fixes for recording, audio and export problems too.

The bigger difference is what happens after the bug appears.

Screen Studio currently has a commercial organization collecting subscriptions and shipping regular reliability updates. Recordly relies much more on whoever is available to reproduce the issue, write the fix, review the pull request and produce the next release.

That distinction becomes important for professional video work because the painful failures often happen late. Losing audio or crashing on a long export can erase the time saved by choosing a free tool.

For casual demos, indie projects and users comfortable with open-source software, Recordly's trade-off can be excellent. For a company that values predictable support more than saving $9 or $29 per month, Screen Studio can still be the easier decision.

So why is recordly.dev free?

Recordly.dev is free because zero pricing has been more useful to the project as a growth and development engine than early subscription revenue would have been.

The pieces fit together unusually well. Recordly entered a category where Screen Studio had already proved demand. It inherited a head start from OpenScreen, moved the expensive recording and rendering work onto users' computers, opened its code to outside contributors and gave people an extremely easy reason to recommend it.

The result is hard to dismiss. Recordly has reached roughly 24,200 GitHub stars, attracted around 1,800 forks and developed a feature set that overlaps significantly with software currently sold for as much as $29 per month.

We also found no convincing evidence that “free” is a temporary trick designed to push users toward a hidden paid tier. Recordly accepts donations and has an extension ecosystem, but neither currently looks like the real business hiding behind the product.

The catch is operational. As we saw previously, the founder's absence left active maintainers without access to existing donation funds and important release credentials. That is a much bigger warning for Recordly than the lack of a subscription.

So the answer is mostly straightforward: Recordly can be free because its architecture is cheap to scale, open source supplies part of the development effort, and free distribution has helped the project grow extremely fast. The harder question now is whether that community can turn a viral open-source project into something that stays reliable and well governed for years.