FileBot

I was running Plex server - so most of my Movies/TV collection has been named using {plex}
Some months ago, I switched to Emby server, using the same {plex} collection files

I've just noticed there's also now an {emby} binding,
So I've switched to using {emby} for naming new content

My Emby server seems quite happy with all the existing {plex} content, so,
What are the differences between {plex} & {emby} ?
Should I consider (somehow) renaming my existing {plex} content, using {emby}

The {emby} binding and the {plex} binding work exactly the same, with slightly different implementation details, e.g. series name and series folder formatting:
viewtopic.php?t=4116

e.g.
Any of these file paths will work just fine for Plex / Emby / Kodi for almost any series, except for the tricky corner cases, that you may or may not have. I wouldn't spend time on hypothetical problems that you (presumably) don't have yet.


If you do need to maintain libraries for Plex and Emby at the same time for some reason, then you'll want to have one master file hierarchy (with xattr) and then auto-generate (offline; using xattr) secondary file hierarchies using hardlinks (i.e. have the same file many times at different file paths without using extra physical disk space) as desired.

@Rednoah

I'm in the same boat except I'm gona use Jellyfin who is a fork of Emby, should I use also the {emby} binding? or would it require an {jellyfin} binding?

There is no jellyfin binding, so you’ll have it pick whichever one generates file paths closest to what jellyfin expects.