Piped

Back to top

An alternative privacy-friendly YouTube frontend which is efficient by design. Piped’s architecture consists of 3 components:

• backend
• frontend
• proxy

Configuration

The backend_url and frontend_url has to be set in the engine named piped and are used by all piped engines (unless an individual values for backend_url and frontend_url are configured for the engine).

- name: piped
  engine: piped
  piped_filter: videos
  ...
  frontend_url: https://..
  backend_url:
    - https://..
    - https://..

- name: piped.music
  engine: piped
  network: piped
  shortcut: ppdm
  piped_filter: music_songs
  ...

Known Quirks

The implementation to support paging is based on the nextpage method of Piped’s REST API / the frontend API. This feature is next page driven and plays well with the infinite_scroll plugin in SearXNG but it does not really fit into SearXNG’s UI to select a page by number.

Implementations

searx.engines.piped.backend_url: list[str] | str = [] : Piped-Backend: The core component behind Piped. The value is an URL or a list of URLs. In the latter case instance will be selected randomly. For a complete list of official instances see Piped-Instances (JSON)

searx.engines.piped.frontend_url: str | None = None : Piped-Frontend: URL to use as link and for embeds.

searx.engines.piped.piped_filter = 'all' : Content filter music_songs or videos

Copyright © SearXNG team

Made with Furo

💾 🌐