Self-hostable async screen recording Snapify is a self-hostable open-source tool for recording the screen, camera, and voice, then sharing recordings asynchronously through public links. Built by Marco Nicola Loparco (MarconLP) and licensed under AGPL-3.0, it positions itself as the self-hostable Loom alternative: record a browser tab, the desktop, or any application, and send a link instead of scheduling a meeting. You can run it on your own infrastructure with Docker or a manual Node.js setup, or opt for the hosted cloud solution.[1][2][3]
Quick verdict
Async video sharing you control Snapify covers the core Loom workflow, unlimited recordings with instant public-link sharing, timed delete or un-listing, and existing-video upload, with data control through self-hosting. The tradeoff is operational: setup spans a database, OAuth apps, S3-compatible storage, and background services, so it suits teams comfortable running a Next.js stack. Public repository signals show around 1,000 stars but a last commit roughly two years ago, so verify maintenance before adopting.[1][2][3][4]
What Snapify can do
Tab, desktop, and application recording Recordings cover browser tabs, the full desktop, and any application, with voice and camera included, and there is no stated cap on the number of recordings.[1]
Instant public-link sharing Each recording gets a public link for immediate viewing, so recipients watch without creating an account.[1][2]
Timed delete and un-listing Recordings can be deleted or un-listed after a specific timeframe, which bounds how long shared videos stay reachable.[1]
Existing video upload Videos recorded elsewhere can be uploaded and shared through the same link workflow instead of re-recording.[1]
Self-host or managed cloud Operators choose between self-hosting the full stack and using the hosted cloud option, keeping the deployment decision with the team.[1][2]
Who Snapify fits
Async bug reports and walkthroughs Teams documenting bugs, giving product walkthroughs, or reviewing work fit the record-once, share-a-link pattern Snapify is built around.[1][2]
Support teams sending visual replies Customer support answering how-to questions with a short recording matches the documented support and collaboration uses.[1][2]
Privacy-minded teams wanting data control Teams that need recordings on their own storage, via their own S3-compatible bucket and database, fit the self-hosted design.[1][2]
Loom-style workflow without seat math Teams wanting Loom-style async recording on infrastructure they control fit Snapify's explicit Loom-alternative positioning, with documented unlimited recordings and free self-hosted use.[1][2]
Limits to weigh
Multi-service self-host setup Self-hosting needs a MySQL database, GitHub or Google OAuth app credentials, S3-compatible object storage, plus QStash, Stripe, Redis, and analytics configuration, which is real operational work.[1][2][3]
Quiet recent maintenance The directory snapshot shows the last commit roughly two years ago despite open issues and pull requests, so adopters should check whether maintenance has resumed.[1][2]
No documented public API The tRPC layer is internal plumbing and no public API is documented, so programmatic integrations cannot be assumed.[1][2]
No enterprise SSO or support plan observed Only consumer GitHub and Google OAuth sign-in is documented, with no enterprise SSO, SLA, or support plan in evidence.[1]
Platforms and deployment
Browser-delivered Web app Snapify is a Next.js web application served on port 3000 that records browser tabs as well as desktop applications.[1][2][3]
Docker and manual installs A multi-stage Dockerfile provides the container path, while the README documents clone, install, environment, and Prisma steps for a manual Node.js setup.[1][2]
TypeScript Next.js stack The codebase runs Next.js 13 with React 18, a TypeScript toolchain, Prisma 4 persistence, and tRPC, with MySQL provisioned for the database URL.[1][2]
Questions worth asking
What is Snapify?
Is Snapify free?
Can you self-host Snapify?
Sources and editorial review
Source research. Reviewed on October 13, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- MarconLP/snapify on GitHub
official · Observed October 12, 2026
Canonical repository page; MarconLP/snapify identity, tagline Screen recording sharing for absolutely everyone, homepage link snapify.it, AGPL-3.0 marker, about 1k stars, 136 forks, 317 commits, open issues and pull requests.
- Snapify README
official · Observed October 12, 2026
Self-hostable Loom alternative positioning; unlimited tab/desktop/app recordings, public-link sharing, timed delete/un-list, existing-video upload; self-host setup with Railway MySQL, GitHub OAuth, Backblaze B2 storage; Pricing-Free badge.
- Snapify LICENSE.md
official · Observed October 12, 2026
Full GNU Affero General Public License version 3 text confirming AGPL-3.0 licensing.
- Snapify package.json
official · Observed October 12, 2026
Next.js 13, React 18, TypeScript toolchain, Prisma 4, tRPC 10, NextAuth, S3 and Stripe SDKs, Upstash Redis and QStash.
- Snapify Dockerfile
official · Observed October 12, 2026
Multi-stage Docker build on Node 18 Alpine producing a standalone Next.js server on port 3000.
- Snapify .env.example
official · Observed October 12, 2026
Database URL, NextAuth with GitHub and Google OAuth, S3-compatible storage, QStash, Stripe billing, Crisp chat, PostHog analytics, Upstash Redis rate limiting.
- Snapify on OpenAlternative
published measurement · Observed October 12, 2026
Directory snapshot; Loom, Screen Studio, CleanShot, Bandicam incumbents, AGPL-3.0, self-hosted Yes, last commit about two years ago, one-click recording and cloud-or-self-host copy.