Jellyfin Segment Editor

Segment editing UI for Jellyfin (Intro/Recap/Outro/Preview/...).

Manage Jellyfin Media Segment positions the simple way. This tool is in early stages of development.

• Create/Edit/Delete all kind of Segments (Intro, Outro, ...)
• Player to copy timestamps while you watch

It can run in two modes:

• Embedded in Jellyfin as a plugin page (recommended)
• Standalone web app that connects to a Jellyfin server you provide

Install (Jellyfin plugin)

The web app is shipped to Jellyfin as the "Segment Editor" server plugin:

• Plugin repo: https://github.com/intro-skipper/segment-editor-plugin

Add the Intro Skipper plugin repository to Jellyfin, then install "Segment Editor" from the Catalog:

https://intro-skipper.org/manifest.json

Note

This URL returns a manifest based on the Jellyfin version used to access it. It will not return a manifest when viewed in a browser (no Jellyfin version is provided).

Requirements

• Jellyfin Server 10.10+
• A segments provider that exposes segment read/write endpoints:
  • Intro Skipper (Jellyfin 10.10.2+)
  • MediaSegments API (Jellyfin 10.10.0 / 10.10.1)
• Standalone mode only: Jellyfin API key (recommended) or a username/password login

Usage

Plugin mode

• Open Jellyfin Web UI -> Dashboard -> "Segment Editor".
• Direct URL: http://myserver:8096/SegmentEditor
• Authentication is inherited from the Jellyfin web UI (no manual API key entry).

Plugin packaging repo: https://github.com/intro-skipper/segment-editor-plugin

Standalone mode

• Start the app, open Settings, and enter your Jellyfin server URL.
• Authenticate using an API key (recommended) or username/password.

API keys can be created in Jellyfin: Dashboard -> API Keys.

Important

In standalone mode, credentials are stored in the browser via localStorage (segment-editor-api). Treat API keys as secrets.

Playback tips

When a file with multiple audio tracks is direct-played, switching the audio track normally requires restarting the stream as a transcode, because most browsers do not expose the HTML audioTracks API.

• Safari supports native in-place audio switching out of the box.
• Chromium browsers (Chrome, Edge, ...) ship the API behind a flag. Enabling "Experimental Web Platform features" in chrome://flags (or launching with --enable-blink-features=AudioVideoTracks) lets the player switch audio in place without interrupting playback. Note that the chrome://flags route enables a broader set of experimental features browser-wide; if the native switch fails for a particular file, the player automatically falls back to the transcode restart.
• Firefox does not implement the API; audio switching always uses the transcode fallback.

Development

Prereqs: Node.js (LTS) and pnpm (see package.json -> packageManager).

pnpm install
pnpm dev

• Dev server: http://localhost:3000
• Tests: pnpm test
• Lint: pnpm lint
• Format/fix: pnpm check
• Mock dev server: pnpm dev:mock starts Vite with a mock Jellyfin server and auto-login when no non-mock login is cached. Set VITE_MOCK_SERVER_AUTO_LOGIN=force to overwrite cached credentials. Use FFMPEG_PATH=/path/to/ffmpeg when ffmpeg is not on PATH.

Build

Standalone build

pnpm build

• Output: dist/

Jellyfin plugin build

pnpm build:plugin

• Output: dist-plugin/
• Uses base path /SegmentEditor/ with a stable entry filename plus hashed chunks/assets for cache-safe embedding.

Hosting notes

The player/subtitle stack benefits from SharedArrayBuffer. If you host the standalone build yourself, you may need cross-origin isolation headers:

• Cross-Origin-Opener-Policy: same-origin
• Cross-Origin-Embedder-Policy: credentialless

(vite dev and vite preview set these headers automatically; see vite.config.ts.)