Back to FloppyChoose Floppy when…
Your media life is larger than your watch history.
You want one self-hosted home for movies, shows, anime, books, games, music, podcasts, ownership, lists, discovery, statistics, imports, and the tools you build around them.
Floppy vs Scrob
A category-by-category comparison.
Both products can track movies and shows. They are optimized for different jobs around that record: Floppy is a broad personal-media system, while Scrob is a focused movie and TV watching, synchronization, and social hub.
The short version.
Choose Scrob when movie and TV watching is the center of your setup and you want a finished live-scrobbling and cross-service sync workflow. Choose Floppy when your history crosses media types and you want one place for tracking, ownership, lists, discovery, statistics, imports, and integrations.
The comparison
What each product does in each category.
The table is the main page. Each row covers one category from the functional comparison, with the practical difference stated in plain language.
| Category | Floppy | Scrob |
|---|---|---|
| Product model | FloppyA personal media database: track what you watch, read, play, listen to, and own in one library and history. | ScrobA movie and TV watching system centered on TMDB titles, shows, seasons, and episodes. |
| Manual live scrobbling | FloppySupports detailed history and playback-driven activity, but does not currently offer the same first-party Start, Pause, Resume, and Stop session flow. | ScrobStart a live movie or episode session, pause it, resume it, stop it, or complete it from the title page. |
| Watched-state synchronization | FloppyHas a provider-neutral watched-state model, change log, conflict handling, checkpoints, and delivery records; provider write coverage varies by integration. | ScrobHas the more complete operational sync story today, with watched state, progress, ratings, and related changes moving between connected services. |
| Playback ecosystem | FloppyConnects to Plex, Jellyfin, and Emby, with Kodi, Stremio, and Nuvio-facing platform work. Some client workflows and write directions are still being verified. | ScrobShips a broader finished movie/TV playback and sync ecosystem across Plex, Jellyfin, Emby, Kodi, Stremio, Nuvio, and ARVIO. |
| Requests and acquisition automation | FloppySupports scheduled Radarr/Sonarr library synchronization and Seerr webhook additions; no equivalent first-party request action from a title page. | ScrobAdd movies and shows to Radarr or Sonarr from Scrob, and automate requests from Plex watchlists, including selected other users’ watchlists. |
| Social functionality | FloppyPublic profiles, shared lists, RSS/JSON feeds, and recommendation workflows make media shareable, but there is no follower graph or title discussion layer. | ScrobFollow users, see activity, and comment on movies, shows, seasons, and episodes inside the tracker. |
| Non-movie/TV depth | FloppyNative support for anime, manga, books, comics, games, board games, music, and podcasts alongside movies and television. | ScrobIntentionally stays focused on movies and television rather than modeling separate media domains. |
| Lists | FloppyPublic/private lists, custom slugs, smart rules, rich sorting, completion data, RSS/JSON feeds, and recommendation approval. | ScrobPersonal and public lists for movies and shows, designed for straightforward curation rather than rule-driven library views. |
| Discovery | FloppyPersonalized rows based on genre, studio, cast, authors, and tags, with persistent hide or not-interested feedback across media types. | ScrobMovie/TV pickers, trending titles, Airing Today, and streaming-aware suggestions answer the immediate “what should I watch?” question. |
| Structured progress | FloppyProgress and time-left behavior across TV, anime, books, and other media, plus ordered progress changes for external clients. | ScrobA dedicated Progress page with Watched and Collection tabs, progress/remaining sorting, complete-series hiding, and separate watched versus collected totals. |
| Collections | FloppyOwned copies across media with source, format, resolution, HDR, codec, bitrate, and adaptable imported custom fields that can feed filters and smart lists. | ScrobPer-file collection records for connected libraries, including technical details such as codec, channels, languages, subtitles, and paths; ownership is centered on movies and episodes. |
| History and statistics | FloppyCross-media history and statistics for watching, reading, listening, and playing, with filters, comparisons, reading streaks, listening time, and duplicate-play cleanup. | ScrobMature movie/TV watch history with multiple plays, timestamps, rewatches, ratings, flexible statistics, and history search. |
| Calendars and notifications | FloppyA broader release calendar with iCalendar feeds and Apprise-based notifications across the media system. | ScrobA focused episode calendar plus detailed theatrical, digital, and physical release schedules for movies. |
| PWA and mobile use | FloppyInstallable as a standalone web app, with mobile-aware layouts and controls. | ScrobInstallable as a standalone web app on mobile and desktop. |
| API and extensibility | FloppyREST, MCP, scoped application credentials, watched/progress feeds, idempotent operations, diagnostics, and published integration contracts. | ScrobFastAPI with interactive OpenAPI documentation through Swagger and ReDoc; a clear conventional REST developer surface. |
| Backup and export | FloppyScheduled recurring CSV exports plus raw database snapshots for ongoing disaster recovery. | ScrobA portable application-level export that can be reimported for migration or restore. |
| Imports and migration | FloppyBroader import ecosystems, including collector and reading workflows, with dynamic field resolution that preserves unfamiliar source columns. | ScrobCan import Floppy/Yamtrack data, but only movie, show, season, and episode records that fit Scrob’s narrower schema are retained. |
| Installation and deployment | FloppyA guided installer can configure Docker or native deployments; the usual stack is the app plus Redis, with SQLite or PostgreSQL. | ScrobPostgreSQL-based, with an omnibus image that packages the application and database into a simpler appliance-style deployment. |
| Metadata and anime | FloppyProvider abstraction across many media types, with dedicated anime identity, provider preferences, and franchise/group routing. | ScrobStrong TMDB metadata with TVDB matching support, but no separate anime or manga domain model. |
| Customization and organization | FloppyConfigurable home rows, table columns, sorting, filtering, smart lists, collection schemas, and media-specific views. | ScrobA tighter movie/TV product with fewer organizational dimensions and a more focused interface. |
One important qualification
Floppy’s synchronization and external-client work is broader than it used to be, but not every provider has the same verified read/write coverage yet. Scrob’s advantage is finished movie/TV synchronization coverage today; Floppy’s advantage is the larger platform around more kinds of media and workflows.
Choose by priority
Which set of trade-offs sounds like yours?
There is no need to pretend the products are interchangeable. Start with the job you want the system to do most reliably.
Choose Scrob when…
Your watching system is the product.
You care most about movie/TV progress, manual live sessions, finished cross-service synchronization, direct Radarr/Sonarr requests, and social activity around what you watch.
Bottom line
Pick the system that matches the question you ask most often.
“What am I watching, where am I watching it, and how should the other services know?” points toward Scrob. “What have I watched, read, played, listened to, and kept—and what should I do with that history?” points toward Floppy.