XBackBone

Open-source file manager for screenshot addicts and homelab builders, honestly reviewed. No marketing fluff.

TL;DR

• What it is: A lightweight, self-hosted PHP file manager built specifically around ShareX — the popular Windows screenshot tool — with support for other upload clients and standard web upload [README].
• Who it’s for: Windows power users who run ShareX constantly and want their screenshots, screen recordings, and files hosted on their own server instead of Imgur or Gyazo. Also homelab builders who want a clean multi-user file sharing host with LDAP and multiple storage backends [README][1].
• Cost savings: Gyazo Pro runs $3.99/month. Keeping files on paid cloud storage (Dropbox, Google Drive) runs $10–15/month. XBackBone costs $0 in licensing (AGPL-3.0) plus $4–6/month for a VPS — and you own the data [README].
• Key strength: The ShareX integration is first-class: XBackBone generates a ready-to-import ShareX config file, meaning setup for a Windows user is literally download config → import → done [website].
• Key weakness: 1,131 GitHub stars is modest, the project is PHP-based (which some self-hosters avoid), AGPL-3.0 has implications if you try to embed it commercially, and the third-party review ecosystem is nearly nonexistent — meaning you’re mostly trusting the project’s own documentation [README].

---

What is XBackBone

XBackBone is a self-hosted PHP file manager centered on one job: being a reliable backend for ShareX, the open-source Windows screenshot and screen recording utility that lets you capture anything and upload it somewhere instantly.

If you’ve never used ShareX, the relevant context is this: ShareX is effectively the power user’s answer to Gyazo and Lightshot. It handles screenshots, screen recordings, GIF captures, file uploads — and it can route all of that to a custom upload destination via a configurable uploader. The problem is that “custom destination” requires a server that speaks the right protocol. That’s what XBackBone is.

The project is written by a single Italian developer (Sergio Brighenti, GitHub: @SergiX44) and sits at 1,131 GitHub stars — a real project with real users, but not a large community. The website is minimal but functional. The documentation lives on GitHub Pages and covers installation, configuration, clients, and common issues. There is no commercial company behind it, no VC funding, no enterprise tier. It’s open source under AGPL-3.0, maintained by a solo developer who accepts PayPal donations and has a Discord server for support [README][website].

What makes XBackBone more than just a ShareX relay is that it also works as a general-purpose file host: web uploads via browser, a media gallery, multi-user management with roles and disk quotas, public and private uploads, LDAP authentication for corporate setups, and storage backends that go well beyond local disk — AWS S3, Google Cloud, Azure Blob, Dropbox, and FTP [README].

---

Why people choose it

The homelab community treats XBackBone as the default answer when someone asks “where should I point ShareX?” The Homelab Wiki, one of the more active Docker self-hosting references, has a dedicated guide for setting up ShareX to work with XBackBone via Docker Compose — which signals that this is a standard pattern in the self-hosted community, not an obscure experiment [1][2].

The reasons that keep coming up:

The ShareX config generator is the killer feature. Other self-hosted options (raw S3 buckets, custom scripts, generic upload servers) require you to hand-configure ShareX’s custom uploader JSON. XBackBone generates and exports that config for you per-user, so a non-technical user can get from zero to “screenshot uploads to my own server” without touching JSON [website].

The storage backend flexibility. Most self-hosted file tools make you commit to local disk. XBackBone lets you back your uploads with S3, GCS, Azure Blob, or Dropbox — meaning if your VPS runs out of space, you switch the backend without migrating the application. For people who already have an S3 bucket or a Backblaze B2 account, this is a meaningful cost optimization [README].

LDAP support for homelabs running unified auth. The LLDAP project — a lightweight self-hosted LDAP server — lists XBackBone as a confirmed compatible service [5]. This matters for anyone running a homelab with centralized user management via Authelia, Keycloak, or a standalone LDAP server. You add XBackBone to the same user directory as Nextcloud, Gitea, and everything else.

Direct embed links everywhere. XBackBone generates direct image links that work natively in Discord, Telegram, and Facebook previews [README]. This is non-trivial: many file hosts generate redirect URLs that embed providers won’t inline. Getting proper OG-preview images out of a self-hosted tool requires specific URL handling that XBackBone does correctly.

The honest caveat: there are almost no independent third-party reviews of XBackBone. The homelab wiki guides are setup instructions, not evaluations [1][2]. If you’re looking for “five people who switched from Gyazo and here’s what they said” — that content doesn’t exist publicly. You’re working from project docs and community reputation, not a trail of comparative reviews.

---

Features

From the README and official website:

Upload and display:

• Images, GIFs, video, audio (with web player), PDF (with viewer), code with syntax highlighting, arbitrary file downloads [README]
• Files preview page for everything [README]
• Public and private upload modes per file [README]
• Direct links compatible with Discord, Telegram, Facebook embed previews [README]

Client support:

• ShareX (Windows) — config generator included [website]
• Screencloud [website]
• uPic (macOS) [website]
• Linux via per-user generated upload script (curl/wget compatible) [README]
• Standard web upload from browser [README]

Storage backends:

• Local disk [README]
• AWS S3 (and S3-compatible: Backblaze B2, Wasabi, MinIO) [README]
• Google Cloud Storage [README]
• Azure Blob Storage [README]
• Dropbox [README]
• FTP/FTPS [README]

User management:

• Multi-user with roles [README]
• Disk quotas per user [README]
• Registration system (enable/disable) [README]
• LDAP authentication [README][5]
• Upload history and search [README]

Organization and discovery:

• Automatic uploads tagging [README]
• Custom tags for categorization [README]
• Media gallery view [website]
• Logging system [README]

Integrations and convenience:

• Share to Telegram [README]
• Bootswatch themes (multiple visual themes out of the box) [README]
• Responsive mobile layout [README]
• Multi-language UI [README]
• In-app system updates — no CLI required for updates [README]
• Web-based installer — no CLI required for initial setup [README]

What’s missing: No built-in album/gallery sharing beyond the media gallery. No built-in CDN. No expiring upload links (time-limited sharing). No native API beyond what’s needed for the upload clients — the REST API is minimal, not a full programmatic interface.

---

Pricing: SaaS vs self-hosted math

XBackBone has no paid tier. It’s AGPL-3.0 software you run yourself. The cost is infrastructure only.

What XBackBone typically replaces:

Service	Monthly cost	Data ownership
Gyazo Pro	$3.99/mo	Gyazo’s servers
Dropbox Plus (for file sharing)	$9.99/mo	Dropbox’s servers
Imgur Pro	~$3.49/mo	Imgur’s servers
Backblaze B2 + custom setup	$1–3/mo + engineering time	Your storage
XBackBone on a $6 Hetzner VPS	$6/mo	Your server
XBackBone + Backblaze B2 backend	~$7–9/mo	Your storage

For a solo user who takes a lot of screenshots — say 100–500 uploads per month — a $6 VPS covers everything with local storage. If you’re managing a small team of 5–10 people all uploading to the same backend, the math stays roughly the same: one VPS, all users share quota. Gyazo Pro per person × 5 people = $20/mo. XBackBone for all five = still $6/mo [README].

The AGPL-3.0 license is free for personal and internal use. If you build a product or SaaS that includes XBackBone, AGPL-3.0 requires you to open-source your entire application. That’s a meaningful restriction for anyone thinking about building a file hosting business on top of it. For internal/homelab use, it’s irrelevant [README].

---

Deployment reality check

XBackBone is a PHP application. That’s the most important fact about its deployment. Unlike Go or Node tools that ship as single binaries, PHP requires a web server (nginx or Apache) with PHP-FPM. The flip side: PHP hosting is the cheapest and most available hosting in existence. If you have a shared hosting plan from Hostinger or SiteGround, you can probably run XBackBone there without a VPS at all.

What you actually need:

• PHP 8.0+ with standard extensions (PDO, GD, JSON, fileinfo, zip)
• Web server: nginx or Apache with mod_rewrite
• Database: SQLite (default, zero configuration) or MySQL/MariaDB
• Storage: local disk minimum, or configured cloud backend credentials
• A domain and HTTPS (via Certbot/Let’s Encrypt or Cloudflare proxy)

Docker path (what most homelab users choose): The Homelab Wiki guide [1] covers this as a Docker Compose stack. The project doesn’t publish an official Docker image, but community-maintained images exist. Most Docker Compose setups pair it with nginx and a PHP-FPM container. This adds complexity versus a Go binary with a single docker run command.

Web installer: XBackBone ships with a web-based installer that runs on first launch and handles database initialization. For non-technical users, this is the right path — you don’t touch a CLI after getting PHP running [website][README].

In-app updates: One genuinely useful feature: XBackBone can update itself from the web UI without requiring SSH access or FTP. For users who deployed it and don’t want to think about maintenance, this reduces the ongoing ops burden significantly [README].

What can go sideways:

• If you’re used to Docker images with no external dependencies (like Gitea or Forgejo), the PHP + web server setup will feel heavier. Expect 1–2 hours to configure nginx correctly for a first-timer.
• File permission issues (web server user vs upload directory ownership) are the most common reported problem in PHP self-hosted apps. XBackBone is no exception.
• The AGPL-3.0 means there’s no commercial support. If something breaks and the Discord doesn’t have an answer, you’re debugging PHP source code.
• LDAP setup requires configuring your LDAP provider separately. XBackBone doesn’t bundle an LDAP server — you point it at an existing one like LLDAP [5].

Realistic time estimate: Technical user on a VPS: 1–3 hours including nginx config and Let’s Encrypt. Technical user via Docker Compose: 30–90 minutes. Non-technical user on shared PHP hosting: 1–2 hours following the documentation step by step.

---

Pros and cons

Pros

• ShareX integration is best-in-class. Generated config files, all upload types supported, nothing to configure manually [website][README].
• Zero licensing cost for personal and internal use. AGPL-3.0 is permissive for everything that isn’t resale [README].
• Multiple storage backends including S3-compatible services — means you can separate compute from storage and scale each independently [README].
• LDAP authentication for homelab users with centralized auth infrastructure [README][5].
• Web-based installer and updates lower the ongoing maintenance bar significantly [README].
• Low memory footprint. The README calls this out explicitly, and PHP-FPM on idle genuinely uses less RAM than a JVM or Electron app [README].
• Multiple upload clients beyond ShareX — Linux script, uPic for macOS, Screencloud [website].
• Direct embed links that work correctly in Discord, Telegram, Facebook [README].

Cons

• PHP is a deployment tax. Compared to single-binary Go tools, the nginx + PHP-FPM setup is more moving parts and more places for permissions and config to go wrong.
• 1,131 GitHub stars and no major third-party reviews. This isn’t a project with a large community or ecosystem. Solo maintainer, limited public discussion [README].
• AGPL-3.0 blocks commercial embedding. If you want to build a product on top of it, you’re either open-sourcing everything or negotiating a commercial license with a solo developer [README].
• No expiring links, no album sharing, no CDN integration. The feature surface is focused on upload+serve, not on link management or access control beyond public/private.
• Docker image situation is unofficial. The project doesn’t publish a maintained official Docker image to a registry — you’re relying on community images or rolling your own [README].
• No SaaS fallback. If self-hosting breaks, there’s no “log in to XBackBone Cloud and your data is there.” Your data lives where you put it.

---

Who should use this / who shouldn’t

Use XBackBone if:

• You use ShareX daily and you’re paying for Gyazo, Imgur Pro, or cloud storage just to have somewhere to host your uploads.
• You run a homelab with LDAP authentication and want a file host that fits into your existing user management.
• You’re comfortable with PHP hosting — either a VPS or shared hosting — and don’t need a single-binary deployment.
• You want to give multiple users (family, small team, Discord community) their own upload accounts on a shared server.
• You want your screenshots to have a permanent home that you control, not an Imgur account that can be nuked if you violate TOS.

Skip it if:

• You don’t use ShareX or a similar screenshot tool. If you just need file sharing, tools like Nextcloud, Seafile, or Filebrowser have broader feature sets.
• You want a Docker image that runs with a single command. The PHP + web server requirement adds configuration overhead that alternatives avoid.
• You’re building a file hosting service for customers. AGPL-3.0 makes commercial embedding legally complicated.
• You need time-limited links, password-protected shares, or fine-grained per-file access controls beyond public/private.
• You’re non-technical and have no one to help with the initial setup. The documentation is solid but assumes familiarity with web server configuration.

---

Alternatives worth considering

• Chibisafe / Zipline — Node.js-based ShareX backends with more active development communities, official Docker images, and broader feature sets (expiring links, chunked uploads). If you want something more modern and actively maintained for ShareX specifically, evaluate these first.
• Chevereto — The heavyweight PHP image hosting option. More polished, larger community, commercial version available. Free version (AGPL-3.0) has more image-focused features than XBackBone. More complex to set up.
• Picsur — A newer, Rust-based image host with a modern UI. Narrower scope (images only, no arbitrary files), single binary deployment, actively developed.
• Lychee — Photo gallery focused, not a ShareX backend. Better if you want a photo album experience rather than a file dump.
• Nextcloud — The obvious alternative if you want file sharing plus everything else (calendar, contacts, office suite). Much heavier, but the feature gap between Nextcloud and XBackBone is enormous in both directions.
• Owncast / Filebrowser — General file managers, no ShareX-specific integration.
• Raw S3 + ShareX — If you already have a Backblaze B2 or Wasabi account, you can point ShareX directly at it without XBackBone. No web UI, no user management, but zero additional software to maintain.

For a Windows user who takes screenshots constantly and wants their own server: the realistic shortlist is XBackBone vs Zipline vs Chibisafe. XBackBone is the most established and documented of the three. Zipline and Chibisafe have more active recent development.

---

Bottom line

XBackBone solves one problem well: it’s a clean, self-hosted backend for ShareX with enough additional features (multi-user, LDAP, multiple storage backends, direct embed links) to make it useful for small teams and homelabs, not just solo users. The PHP stack is a genuine deployment friction compared to newer single-binary alternatives, and the solo-maintainer reality means the community and review ecosystem around it is thin. But it’s been around long enough to be trusted, the web installer and in-app updates lower the maintenance burden, and for the target use case — a ShareX power user who wants to stop paying Gyazo or trusting Imgur — it does exactly what it says. If PHP hosting is already in your toolkit, XBackBone is the obvious first choice. If you’re starting from scratch on a VPS, take twenty minutes to evaluate Zipline or Chibisafe alongside it before committing.

If the deployment step is what’s standing between you and owning your uploads, upready.dev handles the setup as a one-time service.

---

Sources

1. The Homelab Wiki — “Setup ShareX to work with Xbackbone from Windows” (Docker Compose guide). https://thehomelab.wiki/books/docker/chapter/docker-compose
2. The Homelab Wiki — Recently Updated Pages (XBackBone reference). https://thehomelab.wiki/pages/recently-updated?page=3
3. Shaynly — “A Catalog of Self-Hosted Free Software Network Services and Web Applications”. https://shaynly.com/self-hosted-free-software/
4. SaaSHub — “Best Office Suites in 2025”. https://www.saashub.com/best-office-suites-software
5. Codeberg — ghassan/lldap (XBackBone listed as LDAP-compatible service). https://codeberg.org/ghassan/lldap

Primary sources:

• GitHub repository and README: https://github.com/sergix44/xbackbone (1,131 stars, AGPL-3.0)
• Official website: https://xbackbone.app
• Documentation: https://sergix44.github.io/XBackBone/