head to head · open source

Invidious vs Navidrome

Invidious has 24,469 GitHub stars, 2,746 forks, 480 open issues and last shipped 2 days ago. Navidrome has 23,632 stars, 1,708 forks, 275 open issues and last shipped yesterday. Invidious leads on adoption by 4% (24,469 vs 23,632 stars). Invidious is written in Crystal under AGPL-3.0; Navidrome is written in Go under GPL-3.0. Invidious has attracted 11% as many forks as stars, Navidrome 7%. Navidrome was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Invidious ★ 24K Navidrome ★ 24K category Miscellaneous

← all 8884 open source comparisons

Side by side

Invidious Navidrome
GitHub stars ★ 24K ★ 24K
License AGPL-3.0 GPL-3.0
Written in Crystal Go
Last push 2026-09-16 2026-09-17
Forks ⑂ 2.7K ⑂ 1.7K
Self-hosting Yes Yes
Data ownership Your server Your server

pick Invidious if

  • You weight community size — 24K stars and counting
  • You want the AGPL-3.0 license terms
  • Your stack matches Crystal
  • You value the larger contributor base for long-term maintenance

full Invidious profile →

pick Navidrome if

  • You want the Navidrome feature set and don't need the biggest community
  • You prefer the GPL-3.0 license terms
  • Your stack matches Go
  • You evaluated both and Navidrome fits your workflow better

full Navidrome profile →

About Invidious

Invidious is an open source, AGPL 3.0 alternative front end to YouTube, written in Crystal, aimed at people who want to watch videos without ads, tracking, or a Google account.

read the full Invidious overview →

About Navidrome

Navidrome is an open source, web based music collection server and streamer written in Go and released under the GPL 3.0 license. It lives in the self hosted media server ecosystem and is intended for users who want to listen to a personal music collection from a browser or mobile device.

read the full Navidrome overview →

More in Miscellaneous

firecrawl ★ 182K Godot ★ 117K Home Assistant ★ 91K OpenCut ★ 90K OpenBB ★ 73K Jellyfin ★ 57K

Related comparisons

jellyfin vs invidious jellyfin vs navidrome jellyfin vs neko jellyfin vs kodi jellyfin vs nuclear jellyfin vs peertube jellyfin vs iptv-sources jellyfin vs ansible-nas firecrawl vs godot godot vs home-assistant firecrawl vs gdevelop firecrawl vs monogame firecrawl vs sbox godot vs gdevelop godot vs monogame godot vs sbox firecrawl vs home-assistant firecrawl vs cratedb firecrawl vs gladys-assistant home-assistant vs opencut godot vs cratedb godot vs gladys-assistant home-assistant vs cratedb opencut vs cratedb

More Media & Streaming projects

Compare either of these against the rest of the Media & Streaming field.

Invidious vs Jellyfin Invidious vs neko Invidious vs Kodi Invidious vs Nuclear Invidious vs PeerTube Invidious vs iptv-sources Invidious vs ansible-nas Invidious vs Anthias Invidious vs tvheadend Invidious vs Ghosten-Player Invidious vs BookWyrm Invidious vs mytv-android

Frequently asked questions

Is Invidious or Navidrome more popular?

Invidious has 24,469 GitHub stars and Navidrome has 23,632. Invidious has the larger community by that measure.

Are Invidious and Navidrome free?

Both are open source. Invidious is licensed under AGPL-3.0 and Navidrome under GPL-3.0. Neither carries a licence fee.

What is the difference between Invidious and Navidrome?

Invidious is written in Crystal and Navidrome in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Invidious or Navidrome?

Choose Invidious if you want the larger community (24,469 stars) or its AGPL-3.0 licence terms. Choose Navidrome if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.