Chevereto: Self-Hosted Image and Video Sharing Platform Since 2007

What Chevereto Is Built For and Who Uses It

Chevereto was first released in 2007 and has been in continuous development since. Its README describes it as a self-hosted media sharing platform that prioritises flexibility and control, enabling users to build and manage a media sharing website on their own server with complete autonomy over the hosting environment and policies.

The core use case is building a site that functions like Imgur or Flickr but runs on your own infrastructure. Because the operator owns the server, there is no third-party platform to shut down the service, restrict content policies, or change terms of use. The README describes this as eliminating the risk of platform restrictions and shutdowns.

The expected users are website operators who need multi-user media sharing with public or private albums, privacy controls, and content management. Chevereto also supports multi-tenant operation, which means a single installation can host multiple independent sites, making it viable for hosting providers or organisations with separate departments that each need their own media environment.

Feature Coverage and Platform Capabilities

Chevereto includes a broad set of features as listed in the README. Media management covers images, videos, categories, tags, and albums with advanced organisation tools. User accounts include registration, profiles, two-factor authentication, and role-based access control. Content privacy is configurable per user or per item.

Performance features include CDN support, caching, and image optimisation. The platform ships with full internationalisation support and includes over 30 language packs. The API allows integration with external systems.

Multi-tenant support is a notable capability: a single Chevereto installation can serve multiple independent sites, each with its own domain, users, and content. This is uncommon in open-source media platforms and makes Chevereto useful in scenarios where a hosting provider wants to offer branded media hosting to multiple customers from a shared infrastructure.

Chevereto Cloud is available for teams who want the Chevereto feature set without managing server infrastructure. The README describes this as handling the infrastructure so you can enjoy Chevereto without any technical overhead.

System Requirements and Installation Paths

Chevereto requires a webserver, PHP, and a MySQL or MariaDB database. Redis is listed as optional. The README points to documentation for specific version requirements for each component.

Installation options cover several common deployment targets. Docker is the recommended approach for teams comfortable with containers; the Docker image is multi-arch, supporting both x86_64 and arm64. VPS installation guides cover providers such as DigitalOcean, Linode, and Vultr. Control panel installations via cPanel and Plesk are documented. Automated installer support is available through Installatron, Softaculous, and SwiftWave.

The download is available directly from `https://chevereto.com/api/download/latest` or as a zip file from the GitHub Releases page. The most recent release at the time of the last repository push was version 4.5.7, released on 2026-08-20.

For users upgrading from an older version, the README provides distinct upgrade guides for Chevereto V3 users moving to V4, and for V2 users, who should skip V3 and go directly to V4. The upgrade path is documented and supported.

The Two License Models and What They Mean in Practice

Chevereto uses a dual-license model. The open-source edition is licensed under the AGPL-3.0. The commercial editions, Chevereto Lite and Chevereto Pro, use a proprietary Chevereto License.

The critical AGPL clause that affects self-hosted deployments is stated explicitly in the README: under the AGPL-3.0, making the software available over a network is considered distribution, and you must provide the source code to users who interact with it remotely. For a public media sharing site, this means your users have the right to request the source code of your installation, including any modifications you have made.

This is not a problem for operators who deploy Chevereto as it is and do not need to keep their modifications private. It becomes a constraint for companies that want to customise Chevereto and host it as part of a commercial product without disclosing those modifications. The commercial license removes this obligation.

Chevereto Lite and Chevereto Pro are both under the proprietary license. The README notes that proprietary licensing does not mean closed source in this case; the source code is accessible but the terms of use differ from the AGPL. A detailed comparison of editions is available at the documentation link in the README.

Where Chevereto Is Not the Right Choice

Chevereto is a multi-user media sharing platform, which means it is not well suited for all self-hosted media storage scenarios.

For personal photo backup and private library management, the platform has more overhead than most individuals need. Chevereto is designed for sharing and publishing, not for private archival. A user who wants a personal Google Photos replacement with automatic device backup will find that Chevereto does not provide automatic device sync.

Chevereto also requires PHP and MySQL, which adds operational complexity compared to single-binary deployments. Teams that want minimal infrastructure with an all-in-one binary or Docker image without a separate database service will find the dependency stack heavier than alternatives.

Finally, the AGPL-3.0 license is not suitable for all commercial deployment models. Teams who need to keep their server-side modifications private must use a commercial license, which is a paid product.

Chevereto vs Immich and the Maintenance Track

Immich is an open-source self-hosted photo and video backup solution aimed at personal and family use, functioning as a self-hosted alternative to Google Photos. The key difference from Chevereto is the use case: Immich is built around automatic device backup, facial recognition, and private library browsing, while Chevereto is a public or semi-public media sharing platform with user accounts, albums, and a social sharing interface. Immich is MIT-licensed. Chevereto is AGPL-3.0 with commercial options. Choosing between them comes down to whether you need automatic device backup and private library management (Immich) or a full media sharing site with multi-user publishing and admin controls (Chevereto).

Chevereto has released three versions in the 4.5.x series since July 2026. The last push to the repository was on 2026-09-22, and the project shows an active release cadence. The codebase uses PHP as the primary language and is hosted at the 4.5 default branch.

Editorial conclusion

Chevereto is appropriate for organisations or individuals who want a mature, self-hosted media sharing platform with multi-user accounts, privacy controls, and multi-tenant support. The AGPL-3.0 license is suitable for public deployments where source disclosure is not a problem, but incompatible with closed-source commercial use without a commercial license. Before deploying, verify that your server meets the PHP and MySQL requirements, and decide whether the AGPL-3.0 terms or a commercial license better fits your distribution model.

Frequently asked questions

Official sources

1. chevereto/chevereto on GitHub
2. License: AGPL-3.0
3. Project website
4. README
5. Releases