DEV Community

selfhosting.sh
selfhosting.sh

Posted on • Originally published at selfhosting.sh

Invidious Vs Piped

#frontend #opensource #privacy #webdev

Quick Verdict

Piped is the better choice for most self-hosters in 2026. It has SponsorBlock integration, more surviving public instances (15 vs 3), a modern Vue.js interface with PWA support, and federated load balancing across instances. Invidious has a larger community (18.7K GitHub stars) and works without JavaScript, but YouTube's aggressive blocking has decimated its public instance network.

Overview

Both Invidious and Piped are alternative YouTube frontends that let you watch YouTube videos without ads, tracking, or a Google account. They extract video data without using YouTube's official API, serving content through a privacy-respecting interface.

Attribute Invidious Piped
Language Crystal Java (backend), Vue.js (frontend)
First release 2018 2021
GitHub stars 18,700+ 9,800+ (frontend)
License AGPL-3.0 AGPL-3.0
Database PostgreSQL PostgreSQL
Extraction Custom Crystal parser NewPipeExtractor (Java)

Feature Comparison

Feature Invidious Piped
Ad-free playback Yes Yes
No tracking Yes Yes
User accounts Yes Yes
Subscriptions (no Google) Yes Yes
Audio-only mode Yes Yes
SponsorBlock No Yes
Return YouTube Dislike No Yes
LBRY integration No Yes
JavaScript required No Yes
PWA support No Yes
Infinite scroll No Yes
Reddit comments Yes No
Import/export subs Yes (YouTube, NewPipe, FreeTube) Yes
Light/dark themes Yes Yes
4K support Yes Yes
REST API Yes (documented) Yes (JSON)
Federated instances No Yes (Matrix protocol)
Multi-region load balancing No Yes
Geo-restriction bypass Limited Yes (via federation)

Instance Health

This is the most important practical difference in 2026. YouTube has been aggressively blocking alternative frontend instances.

Metric Invidious Piped
Public instances (March 2026) 3 15
CDN-backed instances 0 5+
Instance regions 3 countries 10+ countries
Official recommendation "Host at home instead" Use piped.video or mirrors

Invidious's public instance list has collapsed from dozens to just 3 due to YouTube's IP blocking. The project now explicitly recommends self-hosting. Piped fares better because its federated architecture distributes load across instances, making it harder for YouTube to block effectively.

Deployment Complexity

Invidious

Invidious requires PostgreSQL and a Crystal binary. The setup is straightforward:

services:
  invidious:
    # Invidious rolling release — no versioned Docker tags published
    image: quay.io/invidious/invidious:latest-arm64  # or :latest for amd64
    ports:
      - "3000:3000"
    environment:
      INVIDIOUS_CONFIG: |
        db:
          dbname: invidious
          user: kemal
          password: kemal
          host: invidious-db
    depends_on:
      - invidious-db

  invidious-db:
    image: postgres:15
    volumes:
      - invidious-db:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: invidious
      POSTGRES_USER: kemal
      POSTGRES_PASSWORD: kemal
Enter fullscreen mode Exit fullscreen mode

Resource requirements: 2 GB RAM minimum (4 GB recommended), 20 GB disk.

Piped

Piped has a more complex stack — separate frontend, backend, and proxy containers plus PostgreSQL:

services:
  piped-frontend:
    # Piped does not publish semver Docker tags — :latest is the only option for all components
    image: ghcr.io/teampiped/piped:latest
    depends_on:
      - piped-backend

  piped-backend:
    image: ghcr.io/teampiped/piped-backend:latest
    volumes:
      - ./config.properties:/app/config.properties:ro
    depends_on:
      - piped-db

  piped-proxy:
    image: ghcr.io/teampiped/piped-proxy:latest

  piped-db:
    image: postgres:15
    volumes:
      - piped-db:/var/lib/postgresql/data
Enter fullscreen mode Exit fullscreen mode

Piped also requires a reverse proxy (Nginx or Caddy) in front, with separate domains for the frontend, backend, and proxy. More moving parts, but more scalable.

Resource requirements: Moderate (not explicitly documented). The Java backend uses more RAM than Invidious's Crystal binary.

Mobile App Ecosystem

Platform Invidious Piped
Android — LibreTube
iOS/macOS Yattee Yattee
Apple Watch WatchTube —
Roku Playlet —
Linux desktop PlasmaTube, TubiTui Pipeline, PlasmaTube
Browser extension Privacy Redirect Piped-Redirects, LibreRedirect

Both projects share some clients (Yattee, PlasmaTube), but LibreTube (Android) is Piped-only and arguably the best mobile YouTube alternative available. Invidious has more niche clients (Apple Watch, Roku).

Performance

Invidious is lighter on the server — Crystal compiles to native code and uses less RAM than Piped's Java backend. However, Piped's federated proxy architecture means video streams can be served from geographically closer instances, potentially giving better playback performance for end users.

Both projects face the same fundamental challenge: YouTube actively tries to block them. Performance depends heavily on how quickly each project adapts to YouTube's anti-bot measures.

Use Cases

Choose Invidious If...

  • You want minimal JavaScript (or no JavaScript at all)
  • You prefer a simpler deployment (fewer containers)
  • You want Reddit comments integrated
  • You have limited server resources (lower RAM requirement)
  • You value a larger community for troubleshooting (18.7K stars)

Choose Piped If...

  • You want SponsorBlock to skip sponsor segments automatically
  • You want Return YouTube Dislike to see dislike counts
  • You want a modern PWA that works well on mobile browsers
  • You want federated instance collaboration for reliability
  • You want geo-restriction bypass through multi-region proxying
  • You're comfortable with a more complex multi-container setup

Final Verdict

Piped wins for most self-hosters in 2026. The SponsorBlock integration alone is a significant quality-of-life improvement, and the federated architecture provides better resilience against YouTube's blocking efforts. The 15 surviving public instances (vs Invidious's 3) demonstrate this resilience in practice.

Invidious remains the better choice if you want a lighter deployment, need to work without JavaScript, or prefer the more established community. Both projects face an uncertain future as YouTube escalates anti-bot measures, so self-hosting either one (rather than relying on public instances) is the safest bet.

Related

Top comments (0)