selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Cliparr logo

Self-host Cliparr

v3.0.1

Browser-based video clipper for personal media servers

ReleaseOpen SourceMIT
Updated9 hours ago
LanguageTypescript
Setup difficultyModerate
MobilePWA
Stars
215
Ports
7171 (HTTP server for Cliparr web app and API), 3000 (Development server port)
Docker
ghcr.io/techsquidtv/cliparr
Install with Docker
Cliparr editor showing video preview, playback controls, and timeline clip selectionCliparr running in narrow mobile layout with dashboard, source controls, and playback actionsCliparr editor showing video preview, timeline clip selection, and subtitle controls

What is Cliparr?

Cliparr is a self-hosted video clipping application for personal media servers. It connects to Plex and Jellyfin to automatically discover active playback sessions, letting you trim clips from what's currently playing. You can also open local video files directly in the browser without uploading them. The editor provides a timeline interface for precise clip selection with zoom and fine-tuning controls. Exports run entirely in the browser using WebCodecs — no server-side FFmpeg required — and support video (MP4, WebM, MOV, MKV), audio (MP3, M4A, Ogg/Opus, FLAC, WAV), and GIF formats. Subtitles can be authored from scratch or imported from the media server, then styled and burned into the exported clip. Metadata such as title, artwork, and timing details from the source media are embedded in supported containers. Cliparr runs as a Docker container (Linux/amd64 and Linux/arm64) on port 7171, stores encrypted provider credentials in a SQLite database, and requires a stable APP_KEY for credential encryption. The UI is a Progressive Web App installable on mobile and desktop. Access control is handled externally via reverse proxy (Authelia, Authentik, Tailscale, WireGuard, etc.) since Cliparr has no built-in user authentication system.

Should you self-host Cliparr?

Cliparr scores 51/100 on selfhost.directory (how scoring works) and ranks #7 of 18 in Video Processing. It has 215 GitHub stars.

It shipped 10 stable releases in the past year. The latest, v3.0.1, came out on 20 October 2026. New versions land roughly every 5 days.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is MIT-licensed and written mostly in Typescript.

Its closest alternative on selfhost.directory is Concat (82/100, 12 231 stars). It scores higher overall, so compare the two before you pick. See Cliparr vs Concat side by side.

Features

  • Browser-based processing
  • Encrypted credential storage
  • Live session discovery
  • Local video clipping
  • Metadata Embedding
  • Progressive Web App
  • Subtitle authoring and burn-in
  • Timeline editing
  • Video, audio, and GIF export

Cliparr README

How to install Cliparr

Install Cliparr with Docker

Docker Engine with Linux containers
Environment variables
APP_KEY (required), PORT, CLIPARR_DATA_DIR, CLIPARR_LOG_LEVEL, CLIPARR_LOG_FORMAT, CLIPARR_LOG_FILE, CLIPARR_LOG_FILE_FORMAT, CLIPARR_LOG_FILE_MAX_SIZE, CLIPARR_LOG_FILE_MAX_FILES, CLIPARR_ALLOW_LOOPBACK_PLEX_URLS, CLIPARR_ALLOW_LOOPBACK_JELLYFIN_URLS

docker run -d
--name cliparr
-p 7171:7171
-e APP_KEY="your-32-char-stable-random-secret"
-v cliparr-data:/data
ghcr.io/techsquidtv/cliparr:latest

Linux containers for linux/amd64 and linux/arm64. Requires stable APP_KEY (>=32 chars) and persistent data volume.

How to configure Cliparr

  • APP_KEYRequired secret for credential encryption. Must be at least 32 characters long.

    Required secret for credential encryption. Must be at least 32 characters long.

    values: Random string >= 32 chars

  • CLIPARR_ALLOW_LOOPBACK_JELLYFIN_URLSfalseAllow Jellyfin URLs that resolve to loopback only for the initial configured origin.

    Allow Jellyfin URLs that resolve to loopback only for the initial configured origin.

    values: true, false

  • CLIPARR_ALLOW_LOOPBACK_PLEX_URLSfalseAllow Plex URLs that resolve to loopback only for the initial configured origin.

    Allow Plex URLs that resolve to loopback only for the initial configured origin.

    values: true, false

  • CLIPARR_DATA_DIR/dataDirectory for SQLite storage.

    Directory for SQLite storage.

    values: Any valid filesystem path

  • CLIPARR_LOG_FILEOptional path for a rotating server log file.

    Optional path for a rotating server log file.

    values: Any valid filesystem path

  • CLIPARR_LOG_FILE_FORMATjsonOptional log file format.

    Optional log file format.

    values: json, pretty, logfmt

  • CLIPARR_LOG_FILE_MAX_FILES5Total number of rotating server log files to keep.

    Total number of rotating server log files to keep.

    values: Positive integer

  • CLIPARR_LOG_FILE_MAX_SIZE10mbMaximum size for each rotating server log file.

    Maximum size for each rotating server log file.

    values: Size with kb, mb, gb suffixes

  • CLIPARR_LOG_FORMATjson dev / pretty prodProduction server console log format.

    Production server console log format.

    values: json, pretty, logfmt

  • CLIPARR_LOG_LEVELdebug/infoServer log level.

    Server log level.

    values: trace, debug, info, warning, error, fatal

  • PORT7171 prod / 3000 devInternal port for the Express server.

    Internal port for the Express server.

    values: Any valid port number

Cliparr releases & version history

FAQ

When should I use Cliparr Convert instead?

Use Cliparr Convert when you only need whole-file conversion without self-hosting. The hosted converter runs in your browser and is separate from the full Cliparr app for Plex, Jellyfin, local sources, and timeline clipping.

Does Cliparr work with Plex and Jellyfin?

Yes. Cliparr can connect to Plex and Jellyfin providers, discover active playback sessions, open the current media, and start clipping from the playback position.

Does Cliparr use FFmpeg?

No. Cliparr processes video, audio, and GIF exports in your browser. You do not need to install FFmpeg.

What does the Cliparr server do?

The server handles media server authentication, encrypted provider records, active playback discovery, and proxy work for media routes. It helps the browser reach authenticated sources, while editing and export processing run in the browser.

Where does Cliparr process video?

Cliparr processes video in the browser. Local files are read directly by the browser; Plex, Jellyfin, and direct media URL sources can route through your self-hosted Cliparr server's media proxy so the browser can preview and export them.

More in Video Processing

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…