Back to FloppySmall fixes
The early work was quality-of-life polish: the kinds of changes that make a tracker easier to use every day.
Floppy vs Yamtrack
Floppy vs Yamtrack: What's Different?
Floppy began as a Yamtrack fork. Since then, the projects have diverged by more than 1,900 commits, 1,400 changed files, and 400,000 added lines of source code. Line count is not a reason to switch software. This page explains what that development means if you already use Yamtrack.
Same roots, different direction.
Floppy retains Yamtrack's core idea: self-host your media history and keep control of your data. It adds more ways to browse, organize, and return to everything you watch, read, play, or listen to.
Where did the divergence go?
1,963commits since the fork point
1,455changed files
413,608added lines of source
Those numbers are context, not a reason to switch by themselves. They represent new media types, new ways to use your history, a much larger integration surface, deeper shared workflows, and a lot of work that makes a long-running self-hosted library safer to trust.
How it got here
The name changed because the scope did.
Floppy did not begin as a plan to replace every other media app. It started with a familiar foundation and a growing list of small improvements. Eventually, the improvements became a direction of their own.
Shared roots
Self-hosting, core tracking, imports, and a personal media history remained the center of the experience.
Bigger scope
Music, podcasts, progress, statistics, lists, collections, recommendations, and integrations moved from ideas into the product.
A new name
Once the project had its own priorities, calling it only a Yamtrack fork made the result harder to explain than Floppy did.
What both still share
You are not starting over.
If you know Yamtrack, the basic mental model still makes sense. Floppy keeps the foundation and spends its energy making that foundation useful across more of your media life.
The same kind of home
Floppy is still a self-hosted place for your own history, rather than another subscription service that owns the relationship with your data.
- Run it on your own hardware.
- Track the media you care about.
- Export your data when you need to.
The same starting point
Movies, TV, anime, books, games, and board games are still part of the shared foundation. The difference is how much more the surrounding experience now does with them.
- One account and one library.
- Imports remain part of the workflow.
- Your history stays portable.
- Board games are shared, not a differentiator.
What changes the experience
What do you actually gain by trying Floppy?
The biggest differences are not a list of extra buttons. They are new ways to use the history you already keep in Yamtrack. Each section below starts with the familiar workflow, then shows what Floppy adds and why it matters.
Track music and podcasts in one self-hosted media library
Yamtrack gives you a place to track the media you already use it for. Floppy adds two full media domains rather than attaching a few listening events to a generic item.
Music has artist, album, and track pages, discography sync, MusicBrainz metadata, cover art, play counts, and listening-time statistics. Podcasts have show and episode pages, episode-level tracking, mark-all-played behavior, and native history and stats. Pocket Casts can keep listening current through ongoing account sync instead of a one-time file import.
What you notice: if your movie and TV history lives in Yamtrack while your listening history lives somewhere else, Floppy is designed to bring both into the same library and timeline.
Turn your media history into personalized recommendations
Yamtrack is primarily a place to record and browse your history. Floppy adds a separate Discover system that uses that history to help decide what should be in front of you next.
Discover learns affinities from the genres, studios, actors, directors, authors, and tags already connected to your library. Recommendation rows refresh in the background, and hiding or dismissing something becomes persistent feedback. That includes negative signals, so the system can learn what you do not want to see as well as what you enjoy.
What you notice: your history stops being only something you look backward through. It starts influencing what Floppy recommends when you are ready for the next movie, show, book, or game.
Track owned media collections, not only what you consumed
A watch history and an ownership history answer different questions. Floppy gives them separate places to live without splitting your library.
You watched Blade Runner years ago. You also own the UHD Blu-ray with HDR, a particular format, and a particular source. Floppy can keep those facts at the copy level, including resolution, format, codec, and bitrate, then connect ownership to detail pages, filters, and smart lists. Plex collection sync can help keep the shelf current.
What you notice: the app can answer both “What have I watched?” and “What do I actually own?” That makes it useful as a media collection tracker, not only a consumption diary.
Build smart lists that maintain themselves
Lists are part of Yamtrack's shared foundation. Floppy extends that idea so a list can keep doing work after you create it.
You can build “everything I own in 4K that I have not watched,” “unfinished books by authors I rate highly,” “PlayStation games in my backlog,” or “movies releasing soon that match a tag.” Rules can use collection status, release state, platform, origin, author, and tags. Public profiles, custom slugs, RSS and JSON feeds, and list recommendations add ways to share the result.
What you notice: your lists become saved questions about your library instead of snapshots you have to rebuild every time your collection changes.
Use a REST API and MCP server to work with your library
Yamtrack is designed to be used through its web interface. Floppy gives scripts, services, and compatible AI tools a supported door into the same library.
/api/v1 covers tracking, search, statistics, lists, integrations, music, podcasts, and discovery. The MCP server lets compatible tools and agents search, track, and manage a Floppy instance conversationally. You can connect a script, Home Assistant, another service, or an AI assistant without scraping the UI.
What you notice: your media history becomes something you can build around, not just something you have to open in a browser.
Connect Plex, Jellyfin, Stremio, and the rest of your media stack
The difference is not only the number of integrations. It is how many parts of a self-hosted media life Floppy can connect back to one history.
Watching, listening, gaming, books, and library automation each have their own useful paths into Floppy. These are not one comma-separated roster. They solve different problems:
Watching
Plex, Jellyfin, Stremio, and Kodi for playback, catalogs, collections, and watch history.
Listening
Last.fm, ListenBrainz, Audiobookshelf, Pocket Casts, and scrobble webhooks.
Gaming
PlayStation Network, Xbox, and Grouvee for the games you play and backlog.
Library automation
Radarr, Sonarr, and Seerr for scheduled syncs, webhooks, and automatic additions.
Books, lists, and data
StoryGraph, MDBList, Storyteller, Hardcover, and other import or metadata workflows.
What you notice: Floppy can sit in the middle of more of the services you already use, instead of asking you to maintain several disconnected histories.
Browse the people, studios, and authors behind your media
A title is often only the beginning of the question. Floppy turns the people and organizations behind it into places you can browse.
Actors, directors, authors, and studios have real pages with credits, filmographies, discographies, top works, and related titles. That means you can move from a movie to the director's work, from a book to an author's other books, or from an album to the artist's discography without treating those relationships as hidden metadata.
What you notice: the library starts behaving more like a connected map of your interests than a stack of isolated entries.
Run a long-term self-hosted media tracker with more safety rails
Self-hosting is already part of Yamtrack's appeal. Floppy puts more of its divergence into the less glamorous question of what happens after you have years of data and something goes wrong.
Floppy adds safer database handling, bounded retries, automatic safety backups around recovery, a recovery page for serious startup problems, and floppy_preflight diagnostics for paths, settings, database state, migrations, and Redis. Logs redact credentials, scheduled exports show their history, and dedicated repair tools cover problems in lists, music, metadata, ratings, anime mappings, calendar data, and duplicate items.
What you notice: most of this work is invisible when everything is healthy. That is the point. It makes Floppy easier to trust with a personal library that keeps growing.
The Yamtrack workflows Floppy takes further
Shared workflows, taken further.
The next layer is less about brand-new product surfaces and more about how much more control and context Floppy gives you inside the workflows both projects share. These are the additions that can make you install the image just to look around.
Finding and fixing metadata
Fix a bad match without losing your history.
If an item matched the wrong provider, Floppy gives you tools to remap it or move its provider identity while preserving the history you have already built around it.
Live time-to-beat data for games.
Floppy can retrieve and refresh HowLongToBeat data, keep it attached to the item, and expose it in sortable and filterable library columns instead of relying only on a one-time CSV import.
Scan a book instead of searching for it.
Use the camera to read a barcode or ISBN while adding a book. It is a small interaction, but it removes a surprisingly annoying part of building a reading library.
Choose how titles and providers behave.
Override metadata manually, choose a preferred provider for each media type, and switch between localized and original titles.
Let missing metadata repair itself over time.
Background backfills can fill in missing fields without blocking the rest of the app or making you repair every entry by hand.
Understanding your history and statistics
Compare the periods that matter to you.
Statistics support comparison mode and custom date ranges, so you can look at a month, a year, a media type, or two different periods instead of accepting one fixed recap.
Reading gets its own useful context.
See pages read, top authors, and reading streaks alongside your broader media history. Books are not forced into a movie-shaped set of numbers.
Clean up duplicate plays from the history feed.
When repeated or imported play events clutter a timeline, Floppy gives you an inline cleanup path instead of making you leave the feed and hunt through settings.
Bring in lists, not only account history.
Import Trakt lists and watchlists, plus MDBList collections, so the list workflows you already use can become part of the same library.
Make list progress easier to understand.
Richer sorting, completion percentages, and media-type breakdowns make a list useful as an active project rather than a pile of saved titles.
Making the interface yours
Build the home screen around your habits.
Choose which rows appear and reorder them from library queries, custom lists, smart lists, or recently played but unrated items.
Choose your own table columns.
Media tables and list tables can be configured independently. Show episodes left, time left, time-to-beat, runtime, time watched, next air date, popularity, or the columns you actually use.
See what is playing now.
Plex, Jellyfin, and Emby webhooks can power a live now-playing card with current playback context and progress.
Use a real per-user theme preference.
Choose light, dark, or system themes without making every user share the same display preference.
Keep account controls close at hand.
Authenticator-based two-factor authentication, recovery codes, and per-user session duration make a multi-user self-hosted instance easier to manage.
Controlling the connections around it
See backup and export history inside the app.
Scheduled exports and backups are visible in settings, so important data protection does not disappear into an invisible cron job.
Scope integrations instead of importing everything.
Choose which Plex libraries trigger webhooks and whether an import is watchlist-only or collection-only.
Keep integration settings persistent.
Seerr allowed users and defaults can persist as preferences, and per-integration status makes it easier to see what is connected and what needs attention.
Get more from Jellyfin playback.
Floppy adds a richer Jellyfin layer with dedicated sync and playback-reporting import, rather than stopping at a basic webhook.
Keep the automation surface supported.
The REST API and MCP server give scripts and services a stable path into the library, so integrations do not have to depend on how the web interface happens to be laid out.
Quality-of-life differences
Small changes that add up.
And then there are the hundreds of things you should not have to think about. None of these is the reason someone first installs Floppy, but together they show how the fork accumulated polish across imports, providers, dates, playback, proxies, settings, and long-running libraries.
Better spoiler protection
Hide unseen episode titles and images with a clear user preference.
More time preferences
Choose time display, week start, and per-user session age instead of relying only on instance defaults.
More forgiving imports
CSV rows do not need to arrive in a strict TV, season, episode order, and import status is visible in settings.
Import history at a glance
Per-integration status and import history make it easier to tell what ran, what changed, and what needs attention.
Cleaner statistics
Repeated or multi-season entries are deduplicated in top-rated views so the results are easier to trust.
Better date editing
Keep second-level precision, clear dates explicitly, and edit episode dates without leaving the current view.
More resilient providers
Bounded retries and rate-limit fallbacks help temporary provider failures feel temporary.
Clearer setup guidance
Credential validation and guidance for services such as Hardcover make integration setup less mysterious.
Configurable auto-login
Set an auto-login username with legacy-variable fallback when a dedicated kiosk or household setup needs it.
More predictable reverse proxies
OAuth and webhook URLs prefer the configured public origin when Floppy runs behind a proxy.
Better playback controls
Jellyfin Mark Played and Mark Unplayed behavior is clearer and easier to configure.
Safer diagnostics
Logs redact credentials, and purpose-built checks expose common deployment problems before they become mysteries.
More reliable local editing
Local-time prefills, in-place edits, and an explicit no-date option remove small tracking chores.
Less provider-specific friction
More date formats, title variants, and provider errors are handled without making you repair the source data by hand.
More flexible book dates
Publication dates with a full date, month and year, or year only are handled without losing useful information.
Clearer browser edge cases
Status dates behave more predictably in Safari, including an explicit way to clear a date when needed.
Friendlier container guidance
Deployment notes call out common Redis service-name collisions before they turn into a confusing compose failure.
After the details
Which direction sounds like you?
The comparison is long because the difference is real. The short version is still simple.
Yamtrack
Choose the experience you already know.
Yamtrack is the natural choice if you want its focused tracker experience and prefer to stay close to the project you started with.
Floppy
Choose the broader daily driver.
Floppy is for people who want that foundation expanded into one self-hosted home for their whole media life, with more ways to browse, organize, and revisit it.
Coming from Yamtrack?
The low-drama version.
Floppy is a different project now, but the move was designed to respect the people and data that got it here.
Is Floppy still Yamtrack?
Floppy started as a fork of Yamtrack, but it has diverged enough to have its own direction, product identity, API surface, and container image. The fork is part of the history; it is not the whole description anymore.
Can I move my Yamtrack data to Floppy?
Yes. Export a CSV from Yamtrack and import it under Floppy's Settings → Import. The formats are compatible, so your data moves over as-is instead of being trapped in a one-way migration.
Can I point my existing Yamtrack container at the Floppy image?
You can reuse the existing setup instead of configuring everything from scratch, but this is a one-way change. Switching from fuzzygrim/yamtrack to ghcr.io/dannyvfilms/floppy runs Floppy migrations against the database, and those migrations cannot be undone by switching the image back.
The safer path is to keep Yamtrack running, export a CSV, try Floppy alongside it with a separate database, and switch over once you are ready. If you reuse the existing database volume, take a backup first and treat the change as permanent.
For new pulls, use ghcr.io/dannyvfilms/floppy.
Does Floppy still include the Yamtrack basics?
Yes. Core tracking, importing, self-hosting, and the personal media-history workflow are still there. Floppy adds more around them; it does not discard the reason the original foundation was useful.
What if I want to keep my options open?
Keep regular exports. The shared CSV format means your history is portable, and Floppy's own backups use the same format. Choosing Floppy does not mean giving up ownership of the data you have already collected.
Bottom line
Yamtrack is the starting point. Floppy is the direction that grew from it.
If you want a focused tracker and the experience you already know, Yamtrack remains a reasonable answer. If you want that self-hosted foundation to cover more of your media life and make your history more useful every day, that is what Floppy is for.