Self-hosted video sharing, honestly reviewed. Built for gamers who want private, shareable links without a SaaS subscription.

TL;DR

What it is: Self-hosted video sharing platform — drop your game clips into a watched folder, get unique shareable links with rich previews [README].
Who it’s for: Gamers and small content teams who want private clip sharing without Streamable’s storage limits, Medal.tv’s watermarks, or the overhead of a full media server.
Cost savings: Streamable Plus runs $9/mo with file size limits; Medal.tv Pro is around $4/mo with a watermark on free tier. Fireshare self-hosted runs on a $5–10/mo VPS with no per-video or per-view pricing.
Key strength: Extremely focused scope — it does link-based video sharing and game-based organization, and it does both well without drowning you in configuration.
Key weakness: Small project with one primary maintainer, 1,222 GitHub stars, and limited third-party review presence. No SaaS fallback, no managed hosting option, and GPL-3.0 licensing means you can’t embed it in a closed-source commercial product without legal friction.

What is Fireshare

Fireshare is a self-hosted video sharing tool built around a single workflow: point it at a directory of video files, and it generates unique shareable links for each one, complete with Open Graph metadata so that pasting the link into Discord or Twitter produces a proper embed with thumbnail [README].

The target user is a gamer with a pile of clips saved by OBS, ShadowPlay, or Medal, who wants to share a highlight without uploading to YouTube (public, indexed, platform risk), without using Streamable’s free tier (720p cap, 250MB limit, watermarked), and without shipping their clip through someone else’s servers.

What Fireshare adds on top of basic link sharing: automatic game-based folder organization with cover art, public and private feeds (private feeds are link-only — unlisted rather than authenticated), optional transcoding to browser-friendly formats, LDAP support for multi-user setups, view counters, video cropping, tags for search, and an RSS feed for new public videos [README].

The project is a one-developer effort by Shane Israel, hosted on GitHub under GPL-3.0, with 1,222 stars and 79 forks as of this review. There’s a live demo at https://v.fireshare.net if you want to see the UI before deploying [README].

Why people choose it

The honest answer: the third-party review coverage of Fireshare is thin. It shows up in a self-hosted newsletter as a version update [1] and gets deployed by hobbyists running personal cloud services [3]. There are no dedicated head-to-head reviews against Medal or Streamable. That’s a useful signal itself — this is a community-oriented project that spreads through word of mouth in gaming and self-hosting circles, not through marketing.

What the primary sources tell us:

Versus YouTube. YouTube is free and unlimited, but your clips are public, indexed, and subject to copyright strikes on in-game audio. You also surrender the link structure — YouTube URLs don’t embed cleanly in Discord with a custom thumbnail you control. Fireshare gives you private-by-default sharing and proper Open Graph metadata without a platform algorithm deciding what happens to your content.

Versus Medal.tv. Medal is built for exactly this use case and has a polished client, auto-capture, and a social layer. The free tier clips at 720p and lower quality, and the watermark is visible. Pro ($4/mo) removes restrictions but you’re on Medal’s infrastructure, which has gone through multiple ownership changes. Fireshare removes the watermark concern entirely and gives you full control, at the cost of setup time and a VPS bill.

Versus Streamable. Streamable’s free tier caps uploads at 250MB and 720p. The Plus plan ($9/mo) raises the cap and removes ads. But the history of Streamable includes acquisition, service changes, and a deleted-content incident in 2023. Self-hosting with Fireshare means the only entity that can delete your clips is you.

Versus running a full Jellyfin instance. Jellyfin is a full media server — great if you want to manage a library of movies and TV shows across devices. For the use case of “I have 400 game clips and I want to share specific ones with a link,” Jellyfin is severe overkill. Fireshare is the right-sized tool.

The developer’s own support responses [2] suggest the project’s main user base is Unraid homelab users. Shane Israel runs the demo site on Unraid behind NPM (Nginx Proxy Manager), which is probably the most common real-world deployment configuration.

Features

Based on the README and project documentation:

Core sharing:

Unique shareable links per video [README]
Public feed (browseable) and private feed (link-only) [README]
Open Graph metadata — links embed correctly in Discord, Twitter, Slack [README]
RSS feed for new public videos [README]
Video view counting [README]

Organization:

Automatic game-based organization by folder structure [README]
Cover art pulled per game category [README]
Video tags for search and categorization [README]
Video cropping — trim clips without re-encoding [README]

Access control:

LDAP support for enterprise/multi-user setups [README]
Admin password via environment variable [README]
Optional upload restriction — you can lock uploads to admin-only [README]

Transcoding (optional):

CPU transcoding with H.264 or AV1 [README]
NVIDIA GPU transcoding via NVENC — H.264 on GTX 1050+, AV1 on RTX 40 series [README]
GPU transcoding requires --gpus=all Docker flag and NVIDIA Container Toolkit [README]
Fallback from GPU to CPU if encoding fails [README]
Off by default — raw streaming works fine for browser-friendly formats [README]

Infrastructure:

Docker-first design with three volume mounts [README]
Docker Compose and bare Docker run supported [README]
Mobile browser support [README]
31 releases as of this review, with active development through at least late 2025 [GitHub]

A self-hosted community member added Fireshare v1.2.14 to their public instance in early 2025, noting it added drag-and-drop upload support [1]. One real-world deployment noted the service was later removed due to low usage [3] — which is an honest data point about who actually uses this long-term versus who deploys it on impulse.

Pricing: SaaS vs self-hosted math

Fireshare has no SaaS offering. There’s no managed cloud tier, no hosted version, no freemium. It’s purely self-hosted. The comparison is entirely against what you’d pay elsewhere.

Fireshare self-hosted:

Software license: $0 (GPL-3.0) [README]
VPS: $5–10/mo on Hetzner, Contabo, or Linode

Streamable:

Free: 250MB limit, 720p, ads
Plus: $9/mo — removes limits and ads, but file size caps still apply
Business: $35/mo+

Medal.tv:

Free: 720p cap, Medal watermark, limited storage
Pro: approximately $4/mo, removes watermark and caps

YouTube:

Free, but public by default, copyright-dependent, no custom thumbnail in Discord embeds

Concrete math for a typical user:

A gamer sharing 50–100 clips a month, averaging 500MB each. On Streamable Plus ($9/mo), you’re fine if clips are under the per-file limit. On Medal Pro ($4/mo), you’re fine until you want full-quality 1440p or 4K clips. Self-hosted Fireshare on a $6 Hetzner VPS is $6/mo with no per-file limits, no per-view limits, and full quality — but you need a domain, HTTPS setup, and some comfort with Docker.

Over a year: Streamable Plus ≈ $108. Medal Pro ≈ $48. Fireshare self-hosted ≈ $72 + setup time.

The math doesn’t scream obvious savings the way it does for Zapier vs. Activepieces. Medal is cheap. Streamable is cheap. The real argument for Fireshare isn’t cost — it’s control, quality, and privacy.

Deployment reality check

The install path is Docker Compose with three required volume mounts [README]:

/data — SQLite database and internal state
/processed — generated poster images and metadata
/videos — your actual video files (point this at your clips directory)

The minimum working command is one docker run call with those three mounts and an ADMIN_PASSWORD environment variable [README]. Docker Compose is more ergonomic for long-term use.

What you need:

A Linux VPS or homelab machine with Docker installed
Enough disk for your video library (Fireshare doesn’t compress by default — you’re serving the source files)
A domain and reverse proxy (Nginx Proxy Manager or Caddy) for HTTPS — required for Discord embeds, since Discord won’t embed HTTP URLs [2]
If you want transcoding: either NVIDIA GPU or CPU headroom for background encoding jobs

What can go sideways:

The Unraid support thread [2] reveals the most common failure mode: reverse proxy configuration. CORS errors appear when the proxy isn’t configured correctly. The developer’s recommendation is NPM (Nginx Proxy Manager) over more complex setups like SWAG. If you use a non-standard reverse proxy configuration and something breaks, expect limited support — the developer is one person who can’t debug third-party proxy stacks without logs and direct server access [2].

Discord embeds require valid HTTPS. If you’re running on HTTP or with a self-signed cert, the Open Graph thumbnails won’t appear in Discord — this is a Discord requirement, not a Fireshare bug [2].

One community deployment added Fireshare to a public multi-service instance and later removed it due to low usage [3]. This is anecdotal but worth naming: if you’re deploying this for a group or community, adoption isn’t guaranteed. People default to familiar tools.

Realistic time for a technical user: 30–60 minutes to a working instance with HTTPS. For someone newer to Docker and reverse proxies: 2–4 hours including troubleshooting DNS propagation.

Pros and Cons

Pros

No per-video or per-view pricing. You pay for the VPS and that’s it. 10,000 clip views costs the same as 10 [README].
Right-sized for the use case. No configuration sprawl. Three volume mounts, one environment variable, done. It’s not a media server — it’s a clip sharer, and it stays in its lane.
Open Graph support works. Paste a Fireshare link in Discord and you get a proper embed with thumbnail. This is the feature people actually need and it’s done correctly [README][2].
Game-based organization is genuinely useful. Automatic folder-to-game mapping with cover art is more organized than a flat video list [README].
LDAP support. Not common in tools this small — means you can integrate it with existing directory infrastructure for team deployments [README].
Optional NVIDIA GPU transcoding. AV1 support for RTX 40 series is current-generation — this isn’t an afterthought [README].
Active release history. 31 releases, drag-and-drop upload added in v1.2.14 [1], Discord embedding issues acknowledged and fixed [2] — the project isn’t abandoned.

Cons

Single-developer project. Shane Israel is the entire support team. Support quality varies — the Unraid thread [2] shows responsive but occasionally defensive communication, especially for non-standard configurations.
GPL-3.0, not MIT. If you want to embed Fireshare in a commercial product or white-label it for clients, GPL-3.0 requires you to open-source your modifications. Fine for personal use, potentially a problem for agencies.
No managed hosting. If you don’t want to run a VPS, there’s no hosted Fireshare tier. You’re entirely on your own infrastructure.
Small community. 1,222 stars is modest. If you hit an edge case, the GitHub issues are your primary resource. There’s no large forum, no paid support, no consultants who specialize in Fireshare.
No real analytics. View counting exists, but there’s no referrer tracking, geographic data, or engagement metrics. Fine for personal sharing, limiting for anyone who wants to know where their clips are being shared.
Real-world abandonment data. At least one documented public deployment removed Fireshare after limited adoption [3]. This doesn’t mean the software is bad — it means shared clip hosting is a niche that requires active promotion to fill.
Transcoding is best-effort. CPU transcoding can be slow on underpowered VPS instances. If you have a large backlog of incompatible formats, expect background job queuing [README].

Who should use this / who shouldn’t

Use Fireshare if:

You produce game clips regularly and you’re currently paying for Streamable or frustrated by Medal’s watermark.
You want Discord-embeddable links that you control — no platform terms changes, no content takedowns from rights-holders, no account bans.
You’re comfortable with basic Docker deployment, or you’re willing to spend an afternoon learning it once.
You have a homelab (Unraid, TrueNAS, a spare machine) and want to use it for more than just storage.
You want LDAP integration for a small team or gaming community to share a clip library.

Skip it (use Medal.tv) if:

You want automatic clip capture built into the tool — Fireshare doesn’t record anything, it just serves what you already have.
You want a social layer — likes, follows, a community feed of other players’ clips.
You’re not comfortable managing a server and you don’t have someone technical to help.

Skip it (use YouTube unlisted) if:

You want large-format video hosting with zero infrastructure management and you’re okay with Google’s terms.
Monetization matters — Fireshare has no ad integration.

Skip it (use Jellyfin) if:

You’re managing a full media library (movies, TV shows, music) alongside clips. Jellyfin handles that whole ecosystem; Fireshare does not.

Skip it (stay on Streamable) if:

You upload fewer than 20 clips a month and the free tier covers you. The setup cost of self-hosting isn’t worth it at low volume.

Alternatives worth considering

Medal.tv — the most direct competitor for game clips specifically. Cloud-based, auto-capture capable, social features, ~$4/mo Pro tier. You’re on someone else’s infrastructure, but the product is purpose-built and polished.
Streamable — general-purpose video sharing. $9/mo for limits removal. No game-specific organization.
Tube Archivist — for archiving YouTube content locally, not for sharing your own clips. Different use case entirely.
Jellyfin — full media server. Appropriate if you’re managing a broad library, overkill for clip sharing.
PeerTube — federated video hosting, more appropriate for content creators wanting a public-facing channel than for private clip sharing.
Immich — photos and videos, but focused on personal photo library management, not shareable clip links.
Limelight (self-hosted) — smaller project, similar niche, fewer features than Fireshare.

For the specific use case of game clips with Discord-embeddable links, the realistic comparison is Fireshare vs. Medal.tv Pro. Medal wins on convenience and social features; Fireshare wins on control and no ongoing platform risk.

Bottom line

Fireshare is the right tool for a specific, well-defined problem: you have game clips, you want shareable links, and you don’t want to depend on a SaaS platform that can change its terms, add watermarks, or fold. The deployment complexity is low for anyone comfortable with Docker, and the core feature — a Discord-embeddable link with a proper thumbnail — works correctly. The trade-offs are equally clear: it’s a one-developer project with a small community, GPL-3.0 licensing, and no managed hosting option. If you go down, you fix it yourself.

For a non-technical founder, this probably isn’t the right tool — the value proposition is control over a small niche use case, not a significant SaaS cost reduction. For a gamer running a homelab, or a small esports team that generates clips regularly and wants a private clip library with clean sharing links, the $6 VPS and an afternoon of setup is straightforwardly worth it.

Sources

selfh.st — This Week in Self-Hosted (27 October 2023). Mentions Fireshare v1.2.14 release with drag-and-drop upload. https://selfh.st/weekly/2023-10-27/
Shane Israel — Unraid Community Forums, [Support] Fireshare thread. Developer support responses on reverse proxy configuration, CORS issues, and Discord embed requirements. https://forums.unraid.net/profile/168827-shane-israel/
forum.hardware.fr — Services proposés par Super-H. Real-world deployment note: Fireshare added to a public service stack in March 2025, removed by January 2026 due to low usage. https://forum.hardware.fr/hfr/reseauxpersosoho/Hebergement/services-proposes-super-sujet_36784_1.htm

Primary sources: