What Letterboxd actually does
Letterboxd is a social film-tracking platform founded in 2011 in Auckland, New Zealand by Matthew Buchanan and Karl von Randow. It grew from 1.8M members in 2020 to 11.4M at end-2023 and 17M by end-2024 — a near-10x expansion in four years, driven by pandemic cinephile communities and TikTok film-culture content.
In September 2023, Tiny Ltd. (Andrew Wilkinson's Canadian holding company, TSXV:TINY) acquired a 60% majority stake at a reported $50–60M valuation. The platform has been profitable since 2019. In December 2025 it launched a transactional Video Store in 23 countries, signaling ambitions beyond pure social tracking.
Late 2025 reporting from The Logic and BetaKit indicates Tiny is seeking a buyer for its Letterboxd stake — raising platform-continuity concerns for communities and developers building on its ecosystem. The only notable OSS alternative is Movary (~1.5k stars), leaving the niche almost entirely uncontested.
Film diary and ratings
Users log watched films with half-star ratings and diary entries. The diary view provides a chronological personal record that forms the core engagement loop.
Social feed and reviews
A social graph of followers/following surfaces friends' ratings, reviews, and watchlist additions. Review likes and comments drive community engagement.
Lists and collections
User-curated and official lists (Top 250, decade collections) are heavily traffic-driven. Lists are a core discovery and SEO surface.
Watchlist management
Users maintain a want-to-watch list with streaming-service availability filters (Pro feature), bridging tracking intent to actual viewing.
Stats and year-in-review
Annual stats pages showing genres, countries, directors, and decade breakdowns — one of the most-shared features each December.
Letterboxd Video Store
Launched December 2025 in 23 countries, offering transactional VOD rentals and purchases directly within the platform — a new revenue stream beyond Pro/Patron subscriptions.
Letterboxdpricing & limits
Based on one user on Patron plan
Where Letterboxd falls short
Tiny Ltd. 60% stake reportedly for sale in late 2025
Tiny Ltd. acquired its majority stake in September 2023 at $50–60M valuation and is reportedly seeking a buyer as of late 2025 per The Logic and BetaKit. For a community platform, ownership uncertainty directly affects moderation policy, product direction, and long-term data security. Users who invested years building their film logs face platform-continuity risk with no data-portability guarantee.
No TV-show support despite being the most-requested feature
Letterboxd is films-only by product philosophy — the founders have repeatedly declined TV support despite years of user demand. This sends users to competing tools like Serializd for TV tracking, fragmenting their media log across multiple services. For any creator-monetization or community platform, supporting the full media diet is an obvious expansion path Letterboxd refuses to pursue.
Android app consistently slower and buggier than iOS
Android users represent roughly 72% of global smartphone users, yet Letterboxd's Android app has a long-documented history of slower feature parity and more frequent crashes versus iOS. Community threads on Reddit and the Letterboxd forums consistently rank this as a top complaint. With 17M members, this affects a statistically significant portion of the user base.
Diary import from other services is manual and clunky
Users migrating from IMDb, Trakt, or spreadsheet logs face a painful manual import process. Letterboxd offers CSV import but the format is rigid and error-prone, with no API-driven migration path from competing trackers. This creates high switching cost in both directions — locking users in while also blocking new users from joining.
Near-zero OSS alternative ecosystem means no fallback
With only Movary (~1.5k GitHub stars) as the sole notable OSS Letterboxd alternative, there is no community-maintained self-hosted fallback if the platform changes monetization aggressively post-acquisition. By contrast, Ghost (53.5k stars) or Listmonk (20.9k stars) provide safety nets for publishing and email tools.
Key features to replicate
The core feature set any Letterboxd alternative needs — plus what you can improve on.
Film database with TMDB API integration
Letterboxd uses The Movie Database (TMDB) as its metadata backbone for film titles, posters, cast, crew, and release data. A custom build should integrate TMDB's free API (with attribution) plus a local PostgreSQL cache to avoid rate limits. You can improve on the original by also integrating Wikidata for director filmographies and IMDB identifiers for cross-platform compatibility.
Personal diary and watchlist with half-star ratings
The diary is a date-keyed log of watched films with ratings (0.5 to 5 stars in 0.5 increments), review text, and watched-on date. A custom build needs a flexible diary schema in PostgreSQL with partial indexes on user_id and watched_date. Half-star support is trivially implemented as a NUMERIC(2,1) field — something Goodreads has famously failed to ship for over a decade.
Social feed with reviews, likes, and comments
The social layer requires a follower graph (user_id → following_id), a feed fanout mechanism (push or pull based on follower count), and reaction/comment threading. At 17M members, Letterboxd uses a hybrid approach. A custom build at early scale can use pull-based feed generation with Redis caching, switching to push fanout above 10K DAU.
Lists and collections (curated and user-generated)
Lists are ordered arrays of film references with titles, descriptions, and visibility controls (public/private). The implementation is straightforward — a lists table with an ordered list_items join table. The custom opportunity is enabling collaborative lists, versioned list history, and lists with mixed media types (films + TV) from day one.
Activity-based recommendation engine
Letterboxd surfaces recommendations based on films liked by people you follow and global popularity within your taste profile. A custom build can start with simple collaborative filtering (users who liked X also liked Y) using pgvector in PostgreSQL, then upgrade to a full embedding-based model as data grows.
Streaming service availability filters
Pro users can filter watchlists by streaming service availability. This requires integration with a streaming availability API (JustWatch API or Streaming Availability API by MovieOfTheNight). A custom build can offer this on the free tier as a competitive differentiator against Letterboxd.
Stats and year-in-review analytics
The stats page aggregates a user's viewing history by genre, country, decade, director, and runtime. This is a pure read-heavy aggregation query — a custom build can implement it with materialized views in PostgreSQL refreshed nightly, and generate shareable image cards via canvas or Puppeteer for social sharing.
Technical architecture
A Letterboxd alternative is a social media platform with a film metadata layer, a follower graph, and a content-feed engine. The core technical challenges are feed generation at scale (fanout vs. pull), TMDB API rate management, and image-heavy UI performance for poster grids. The recommendation engine starts simple but becomes the key moat differentiator.
Frontend
Next.js App Router, Nuxt 3, SvelteKit
Recommended: Next.js App Router — ISR for public film pages and list pages enables SEO at scale without server load; 'use client' only for feed and interactive diary.
API / Backend
Node.js (Fastify/Express), Go, Django REST Framework
Recommended: Node.js with Fastify — fast startup, excellent ecosystem for social app patterns, pairs naturally with Next.js monorepo.
Database
PostgreSQL, MySQL, PlanetScale
Recommended: PostgreSQL — native support for pgvector (recommendations), JSONB for flexible film metadata, and partial indexes for social feed queries.
Film Metadata
TMDB API, OMDB API, OpenLibrary (for book adaptations)
Recommended: TMDB API with local PostgreSQL cache — free with attribution, comprehensive, and the de-facto standard for indie film apps.
Auth
Supabase Auth, Auth.js v5, Clerk
Recommended: Supabase Auth — handles OAuth (Google, Apple) and email/password with built-in RLS policies that map cleanly to follower-based content access.
Image Storage and CDN
Cloudflare R2, AWS S3 + CloudFront, Supabase Storage
Recommended: Cloudflare R2 with Images resizing — zero egress fees, automatic responsive image generation, and global CDN for poster-heavy pages.
Search
Algolia, Meilisearch, PostgreSQL full-text
Recommended: Meilisearch — self-hosted, fast, and cost-effective for film title search with typo tolerance; upgrade to Algolia at commercial scale.
Complexity estimate
Complexity 7/10 — the social graph and feed fanout are the hardest engineering problems. Plan for 4–6 months with a team of 2–3 experienced developers. TMDB API integration is straightforward but the recommendation engine adds significant scope.
Letterboxd vs building your own
Open-source Letterboxd alternatives
Existing projects you can self-host or use as a starting point. Each has trade-offs.
Movary
1.5kMovary is a self-hosted personal movie and TV log built in PHP. It offers diary tracking, ratings, watchlists, and basic stats — the core Letterboxd experience without the social layer. It integrates with TMDB for metadata and supports Trakt/Letterboxd CSV import.
BookWyrm
2.6kBookWyrm is a federated book-tracking social network built on ActivityPub using Python/Django. While book-focused, its architecture (ActivityPub federation, social reading log, review system, shelves) is highly analogous to what a federated Letterboxd replacement would need.
FreshRSS
15kFreshRSS is a PHP-based self-hosted RSS/feed aggregator. While not a film tracker, it represents mature PHP infrastructure for content consumption and curation — relevant as a feed/discovery layer for a custom media platform.
Build vs buy: the real math
4–6 months
Custom build time
$60K–$150K
One-time investment
Not applicable for direct fee savings — build rationale is community ownership and feature differentiation
Breakeven vs Letterboxd
Letterboxd Pro is $19/yr and Patron is $49/yr — the SaaS cost is trivially low compared to any build cost. The build rationale is not cost savings but community ownership, TV-show support, niche differentiation (e.g., animation-only, horror-only, a specific regional cinema community), and protection against the Tiny Ltd. ownership transition. A $60K–$150K custom platform serving a 10K-member niche community with memberships at $5/mo generates $50K/mo — recouping agency costs in 1–3 months. The software is relatively approachable at complexity 7/10; the challenge is building the community moat that makes Letterboxd valuable in the first place. Build only with a clear community differentiation thesis — not as a generic Letterboxd clone.
DIY roadmap: build it yourself
This roadmap targets a social film-tracking MVP with diary, ratings, social feed, and TMDB integration. It assumes a team of 2 developers using Next.js, Supabase, and TypeScript.
Foundation and metadata layer
3–4 weeks- Set up Next.js App Router project with Supabase auth (email + Google OAuth)
- Design PostgreSQL schema: users, films (TMDB cache), diary_entries, ratings, watchlist
- Build TMDB API integration with local caching layer to avoid rate limits
- Implement film search with Meilisearch backed by TMDB data
- Build film detail pages with ISR (revalidate every 24h)
Core diary and ratings features
3–4 weeks- Build diary entry form with date picker, half-star rating (0.5 increments), and review text
- Implement watchlist add/remove with streaming availability API integration
- Build personal stats page with aggregations by genre, country, decade, and director
- Add CSV import for Letterboxd and Trakt export files
- Build user profile pages with diary, ratings, and list views
Social graph and feed
4–5 weeks- Implement follow/unfollow with follower_graph table and RLS policies
- Build pull-based social feed showing followed users' diary entries and reviews
- Add likes and comment threading on reviews
- Implement activity notifications (new follower, like, comment) via Supabase Realtime
- Build list creation with ordered film arrays and privacy controls
Discovery and recommendations
2–3 weeks- Build popular films feed based on recent community diary activity
- Implement basic collaborative filtering: users who rated X highly also rated Y
- Add genre and decade browse pages with pagination (ISR)
- Build year-in-review stats page with shareable image generation via Puppeteer
- Add RSS/ActivityPub feed for public user profiles
Monetization and polish
2–3 weeks- Integrate Stripe for Pro/Patron subscription tiers
- Implement streaming availability badge on film pages (JustWatch API)
- Build admin moderation panel with user management and content flags
- Add Cloudflare R2 for user avatar and list cover image uploads
- Performance audit: image optimization, ISR coverage, database index review
These estimates assume 2 experienced Next.js developers. Solo builders should add 60–80% to each phase. The recommendation engine is a rough V1 — a production-quality taste-matching system requires significantly more data science work beyond this roadmap.
Features you can't get from Letterboxd
This is where a custom build pulls ahead — features impossible or impractical on a shared platform.
TV show and episode-level tracking alongside films
Letterboxd refuses to support TV shows by product philosophy. A custom build can integrate TMDB's TV API to enable season/episode-level logging, ratings per episode, and unified film+TV stats. This directly captures the largest unfulfilled user request on the platform.
Federated ActivityPub network between film communities
A custom platform can implement ActivityPub federation so that a horror-film community instance can federate with a French-cinema instance — users follow each other across instances. Letterboxd is a walled garden with no federation. BookWyrm's ActivityPub implementation is a direct reference architecture for this.
AI-powered personalized film recommendations with taste profile
Using pgvector and OpenAI embeddings on a user's rating history, a custom build can generate natural-language taste profiles ('You gravitate toward 1970s European arthouse films with ambiguous endings') and explain why each recommendation was made. Letterboxd's recommendation engine is a black box.
Niche community tools (curated clubs, watch-alongs, live discussions)
Letterboxd has no live events or structured watch-along features. A custom platform can add film club rooms with synchronized watching timestamps, live comment streams, and scheduled watch-along events — features that drive retention and premium subscriptions.
Director and cinematographer deep-dive analytics
Letterboxd stats are user-centric (your viewing). A custom platform can offer creator-centric analytics: every Kubrick film ranked by your rating, a breakdown of cinematographers you've watched most, and a 'films you should have seen' gap analysis. This is a differentiator no existing tool offers.
Who should build a custom Letterboxd
Niche film communities (horror, animation, regional cinema)
A custom platform can be purpose-built for a specific genre or regional cinema scene — Arabic film enthusiasts, J-horror collectors, Criterion obsessives — with community governance, curator roles, and genre-specific metadata that Letterboxd's one-size-fits-all approach cannot serve.
Film schools and academic institutions
Film schools need cohort-based tracking (all students logging the same curriculum), instructor annotations, and private class lists — none of which Letterboxd supports. A custom build with LDAP/SSO and cohort features serves this vertical directly.
Streaming services and studios building loyalty features
A streaming service or studio could embed a branded film-tracking layer directly into their app — users log what they've watched on the platform, earn recognition, and receive personalized recommendations. Letterboxd cannot be white-labeled or embedded.
Developers who want ActivityPub-native social film tracking
The fediverse has no mature film-tracking instance. A developer who builds a well-maintained Letterboxd-style ActivityPub server fills a real gap — BookWyrm proved the federated social book-tracking model works at ~40K registered users.
Skip the DIY — let RapidDev build it
Everything above is doable — but it takes months of full-time work. We build custom Letterboxd alternatives using AI-accelerated development, delivering in weeks what used to take quarters.
Discovery call (free)
30 minWe map your exact requirements: which Letterboxd features you need, what custom features to add, your users, integrations, and compliance needs. You get a detailed scope document and fixed-price quote within 48 hours.
AI-accelerated build
4–6 monthsOur engineers use Claude Code, Lovable, and custom AI tooling to build 3–5x faster than traditional development. You see progress in a staging environment every week — not a black box for months.
Launch + handoff
1 weekWe deploy to your infrastructure, transfer the GitHub repo, set up CI/CD, and walk your team through the codebase. You own 100% of the source code — no vendor lock-in, no recurring platform fees.
What you get
Timeline
4–6 months
Investment
$60K–$150K
vs Letterboxd
ROI in Not applicable for direct fee savings — build rationale is community ownership and feature differentiation
30-min call. Fixed-price quote within 48 hours. No commitment.
Frequently asked questions
How much does it cost to build a Letterboxd alternative?
A custom Letterboxd alternative costs $60K–$150K with an agency team of 2–3 developers. The low end covers a solid MVP with diary, ratings, social feed, and TMDB integration. The high end adds a recommendation engine, streaming availability filters, and TV-show support. Solo developers can build a personal tracker like Movary in a weekend, or a social MVP in 2–3 months.
How long does it take to build a Letterboxd clone?
Plan for 4–6 months with a team of 2–3 experienced developers. The core diary, ratings, and TMDB integration take 4–6 weeks. Social features (follow graph, feed, comments) add another 4–5 weeks. A recommendation engine and stats/analytics add 2–3 weeks each. Solo builders should double the timeline.
Are there open-source Letterboxd alternatives?
The main OSS option is Movary (~1.5k GitHub stars, MIT), a PHP self-hosted personal movie log with diary, ratings, and Trakt/Letterboxd import. It covers the solo-tracker use case but has no social features. BookWyrm (2.6k stars, AGPL-3.0) is a federated ActivityPub social tracker built for books — its architecture is directly adaptable for film. There is no production-ready OSS Letterboxd social clone.
Can RapidDev build a custom Letterboxd alternative?
Yes. RapidDev has built 600+ apps including social platforms, media tracking tools, and recommendation engines. We can deliver a custom film-tracking platform with social features, TMDB integration, and optional ActivityPub federation. Book a free consultation at rapidevelopers.com/contact.
Should I worry about Letterboxd shutting down or changing?
The risk is real but not imminent. Tiny Ltd.'s 60% stake is reportedly for sale as of late 2025. If a new acquirer changes the pricing model or platform direction, 17M members face a disruptive migration with limited data portability (Letterboxd offers CSV export for diary data only). A self-hosted alternative eliminates acquisition risk entirely.
Why doesn't Letterboxd support TV shows?
The founders have stated this is a deliberate product philosophy — Letterboxd is a film platform. Despite it being the most-requested feature category for years, the team has declined to add TV support. Any custom alternative built on TMDB's API can support both films and TV shows (including episode-level tracking) from the first week of development.
Can I import my Letterboxd data into a custom build?
Yes. Letterboxd offers CSV export of your diary, ratings, watchlist, and lists. A custom platform can parse this format directly. Building an import tool typically takes 1–2 days and covers all Letterboxd data types. Trakt also offers export, giving you a broader migration surface.
Do I need a TMDB API key to build a film tracker?
Yes. The Movie Database (TMDB) API is the standard metadata source for indie film apps and it's free with attribution. You get full film, TV, cast, crew, and poster data. Rate limits apply (40 requests/10 seconds on the free tier), so caching TMDB responses in PostgreSQL is essential to avoid hitting limits and to reduce latency.
We'll build your Letterboxd
- Delivered in 4–6 months
- You own 100% of the code
- No per-seat fees, ever
30-min call. No commitment.