Progress
Always know where you left off.
Track episodes individually, see what is in progress, and keep next-air information close to the shows you are following.
Episode-level progress · continue watching · next up
For people leaving Trakt
Floppy is a self-hosted Trakt alternative for people who do not want years of watch history, episode progress, lists, and ratings tied to one hosted account. Bring the history with you, keep the workflows you rely on, and let Plex, Jellyfin, and the rest of your stack keep it current.
One glance at what is next.
Bring the database, keep the workflows, connect the stack, and own the next copy.
Keep the system
The point is continuity, not a feature checklist. Floppy gives your progress, lists, collection, calendar, and availability workflows a durable home, with clearer boundaries between them.
Progress
Track episodes individually, see what is in progress, and keep next-air information close to the shows you are following.
Episode-level progress · continue watching · next up
Lists + collection
Keep your watchlist for what comes next. Use custom and smart lists for how you organize it. Keep your owned collection separate, with source, format, resolution, HDR, and other copy details when you care about them.
Watchlist · smart lists · owned copies
Calendar + availability
Use the month and day calendar, an iCal feed, media-type filters, and watch-provider filters shaped around your region and pinned services.
Calendar · iCal · providers · local region
Bring the years with you
Move the record you already built, then keep using it. Floppy has a Trakt import path today, with both live-account and file-based routes.
Supported today
Import your history, ratings, Watchlist, and custom lists. Original watched-at dates and repeat watches are preserved where the source provides them. The import is its own workflow. You do not need to keep Trakt as an ongoing dependency.
Connect the stack
Your tracker is only one piece of the workflow. Floppy can sit beside the media servers, scrobblers, request tools, and automations you already run.
Media servers
Bring media-server activity and library context into the same history. Plex and Jellyfin support live events plus backfill; Kodi’s path is webhook-based. Kodi users can get a bit more functionality through Umbrella.
Automation
Use the documented REST API, API-key or bearer auth, and MCP server for the automations that make a self-hosted library feel like yours.
A clear fit
If you used Trakt as a database and tracking tool, Floppy is built around that same continuity, with a different home for the data.
Floppy is a personal, self-hosted media library, not a hosted social network or a promise to reproduce every Trakt screen. The trade is straightforward: more control over your data, with a product that keeps growing around your own media life.
And then you get more
Once the core workflow is in one place, music, podcasts, books, games, collections, stats, and person pages can live alongside it instead of becoming another silo.
Bring your history home
Start with the system you already understand, then give it a home that belongs on your server.