MediaForge
MediaForge is a self-hosted media ingest engine, packaged as a single Docker container, that handles the complete journey of a raw video file from arrival to…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
57/100 Fair
- Maintained
- 88last commit 23 days ago
- Popular
- 176 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 26 days ago
- GitHub stars
- 6
- Open issues
- 0
- Last commit
- 2026-10-29
- Latest release
- v1.9.1
- License
- MIT
- Activity
- declining
Checked 8 days ago - source: GitHub (braydin72/mediaforge)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install ffmpeg and ffprobe first MediaForge needs ffmpeg and ffprobe (the programs that actually process media). Put them on your PATH (the folders your terminal searches for commands) or set FFMPEG_PATH and FFPROBE_PATH to the exact file locations; otherwise MediaForge commands will fail. source
- Install MediaForge the way you'll use it If you plan to type mediaforge commands, run npm install -g mediaforge so it is available from any terminal. If you are building a code project that uses MediaForge, run npm install mediaforge in that project instead; the wrong choice can cause 'command not found' or import errors. source
- Check hardware acceleration first If you want faster GPU processing, run mediaforge caps --hwaccels first and then use only a listed accelerator with its exact device path. If the accelerator is missing or the path is wrong, the command can fail. source
- GPU Setup (Recommended) Without GPU passthrough, MediaForge falls back to slower CPU encoding. Enable GPU passthrough in your container settings for best performance. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which API keys do I need to configure for identification?
TMDB is required for movies, and TVDB is required for TV shows. OMDb can be added as an optional fallback.
What should I use for the /staging volume?
Use fast storage such as an SSD or cache pool. It is intended for encode working files.
What port does the web UI use?
The web UI runs on port 8080. Expose 8080 in Docker Compose and access the server IP at that port.
What happens if a file cannot be processed automatically?
It does not fail silently. The file is placed in the Review Queue with a specific reason.
Is there a maximum file size?
Because processing is local, the limit depends on device memory. Files under 2GB are generally recommended for stability.
Answers sourced from github.com, mediaforge-official.vercel.app
Community
- Which media server to choose? : r/selfhosted - Reddit (reddit)
- Is there a self hosted media player? : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads