Piwigo

Open-source photo management, honestly reviewed. For individuals escaping cloud photo fees and organizations tired of per-seat storage pricing.

---

TL;DR

• What it is: Open-source (GPL-2.0) photo management software for the web — think self-hosted Google Photos for teams and individuals, built and maintained since 2002 [4].
• Who it’s for: Photographers, small organizations, and non-technical founders who need fine-grained album control, multi-user access management, and data sovereignty without paying per gigabyte [3][4].
• Cost savings: Google Photos charges $2.99–$9.99/mo per user for storage tiers. Piwigo self-hosted runs on a $5–10/mo VPS with no per-storage fees and no per-user charges. For a team of 10 sharing 500GB, the savings are immediate.
• Key strength: Longevity and stability. Born in 2002, actively maintained through 16+ major versions, 200+ plugins, and a community that has outlasted most of its competitors — Zenphoto, Gallery, and Koken among them [website][4].
• Key weakness: It is not a modern SaaS product. The setup requires PHP, MySQL, and a web server — not a Docker Compose file. The UI is functional but not polished by 2026 standards, and the mobile apps are basic compared to Google Photos’ intelligence features [3][4].

---

What is Piwigo

Piwigo is a web-based photo gallery application. You install it on a server, point it at a domain, and you have a self-hosted photo library with albums, batch upload, user management, and public/private sharing. The company behind it is French, the project started in 2002, and version 16.3.0 shipped three weeks before this review [website].

What makes Piwigo distinct from the newer wave of self-hosted photo tools (Immich, PhotoPrism) is its explicit orientation toward organizations and teams, not just personal libraries. The homepage quotes come from a Swiss outdoor equipment manufacturer using it as an internal image database for global distributors, a French tourism office running a hybrid internal/public photo library, and a photographer who has used it for over a decade [website]. This is not software built for one person syncing iPhone photos — it’s built for managing large, multi-user collections with controlled access [4].

The project sits at 3,756 GitHub stars. That number is modest by modern open-source standards but misleading as a health signal — the project predates GitHub, has a stable long-term user base, and has been shipping continuous updates for over two decades [merged profile][website].

---

Why people choose it

The pattern across the available reviews is consistent: people choose Piwigo when they need control over who sees what, large volume without per-storage pricing, and something that will still work in five years.

The sustainability argument. The It’s FOSS review [4] opens with the Google Photos angle, but the more durable case is in a testimonial from Ulf Tietjen: he moved from Koken (now dead) to Piwigo in 2020 specifically because “Piwigo’s history was enough reason to expect a system with ongoing maintenance and development” [website]. This is the trust argument that actually matters for non-technical founders — they’ve already been burned by a tool going unmaintained. A project that shipped in 2002 and is still active in 2026 has survived more software cycles than most of its competitors.

The organization use case. Piwigo’s strongest selling point compared to consumer photo services is the permissions system. Kurt Gerber of EXPED (Swiss outdoor gear) uses it specifically because it supports “different, password-protected levels” that let distributors and dealers worldwide access product images “according to their access authorization” [website]. This is a use case that requires a commercial DAM (Digital Asset Management) solution or a cumbersome workaround on Google Drive — Piwigo handles it natively with its group and album permission system [4].

Privacy and data location. The It’s FOSS review [4] positions Piwigo as a Google Photos alternative primarily on the privacy axis: your photos don’t pass through Google’s servers for face recognition, object detection, or ad targeting. For the cloud hosting option, data is stored in France with backups — relevant for European organizations with GDPR obligations [4].

High volume without degradation. The homepage explicitly calls out “high volume” as a core strength: “Piwigo shines when it comes to classifying thousands or even hundreds of thousands of photos” [website]. The SaaSHub comparison [3] lists scalability as a feature: “Piwigo can handle large galleries containing thousands of photos efficiently.” Consumer services throttle or charge for scale; Piwigo is built for it.

---

Features

Based on the official website, README, and the It’s FOSS review [4]:

Core gallery management:

• Album hierarchy with nested albums [website]
• Batch management — bulk operations on large collections [website]
• Tags with EXIF/IPTC metadata reading and editing [2][4]
• Filters to quickly find photos by album, tag, date, or metadata [4]
• Drag-and-drop file upload [2]
• Bulk content importer for large migrations [2]
• Watermarking support [2]
• Resize, rotate, and color-change functions [2]

Access and sharing:

• Public and private mode per album [4]
• Group-based user permissions — assign groups to albums, not individuals [4]
• Password-protected albums [1][2]
• Share photos by link [4]
• Custom subdomain on cloud hosting (*.piwigo.com) or custom domain on self-hosted [4]

Multi-user and organizational:

• Full user management with roles [3][4]
• Support for organizations with multiple access levels [website][4]
• Email notifications [4]
• Basic analytics for storage and usage tracking [4]

Extensibility:

• 200+ plugins for batch management, comments, expiration controls, upload extensions, anti-spam, and more [website][4]
• Theme support — installable skins for the public-facing gallery [website]
• Multi-language UI [3][website]
• External storage server support [2]
• One-click system updates [2]

Mobile:

• iOS and Android apps for upload and browsing [4]
• Mobile-responsive web interface

File support:

• JPG/JPEG, PNG, GIF for individual accounts on cloud hosting [4]
• All file types for enterprise/self-hosted (including video) [4]
• RSS feeds [2]

What’s notably missing: There is no AI-powered search (faces, objects, scenes), no automatic tagging from machine learning, no duplicate detection, and no timeline view comparable to Google Photos or Apple Photos. If those features matter to you, Piwigo is not the right tool [4].

---

Pricing: SaaS vs self-hosted math

Piwigo cloud (piwigo.com): The cloud hosting option exists for users who don’t want to manage their own server. Pricing tiers are not publicly listed in detail on the scraped pages, but the website mentions a 30-day free trial and individual hosting with unlimited storage on the cloud tier [4]. Exact pricing data is not available for this review — check piwigo.com directly.

Self-hosted (GPL-2.0 community edition):

• Software: $0
• VPS to run it: $5–10/mo (Hetzner, Contabo, DigitalOcean)
• Hosting requirements: PHP 7.4+, MySQL 5+, Apache or nginx, ImageMagick [README]
• Your time: more on this below

Comparison with common alternatives:

Google Photos: Free up to 15GB shared across Google account. After that: $2.99/mo for 100GB, $9.99/mo for 2TB — per Google account. For a team of 10 each needing 100GB, that’s $30/mo or $360/year, growing as photo libraries grow.

Flickr Pro: $8.25/month or $72/year per account — unlimited photos, one user. Fine for individuals, doesn’t scale to organizations.

SmugMug: $9–$45/mo depending on tier. Full-featured photo hosting but SaaS with no data export flexibility.

Self-hosted Piwigo on a $6 Hetzner VPS: $72/year, unlimited photos, unlimited users, all features. A 10-person team that would pay $360/year for Google One each saves roughly $3,500/year by self-hosting. That’s the math that shows up in r/selfhosted and r/PhotoManagement consistently.

The honest caveat: this comparison only works if you already manage servers, or you’re willing to pay someone to set it up once.

---

Deployment reality check

Piwigo is a traditional PHP web application, not a modern Dockerized service. This is simultaneously its strength (runs on nearly any hosting) and its friction (the setup path is more manual than tools like Nextcloud or Immich).

What you need:

• A web server — Apache or nginx recommended [README]
• PHP 7.4+ (7.0+ technically works but is end-of-life) [README]
• MySQL 5+ or MariaDB equivalent [README]
• ImageMagick (recommended) or PHP GD for image processing [README]
• A domain name and SSL certificate

Two install paths:

• NetInstall: Download a PHP script, transfer it via FTP, run it in a browser. Guided install wizard. Recommended for non-technical users on shared hosting [README].
• Manual: Download and unzip the full package, upload via FTP, run the install wizard. More control [README].

No Docker Compose file in the official README. The website mentions Docker support (the 16.3.0 changelog references a Docker update), but it’s not the primary deployment path the project documents. If you’re coming from tools like Immich or Photoprism where you paste a docker-compose.yml and run one command, Piwigo’s install experience will feel dated [website changelog].

What shared hosting means: Because Piwigo runs as a PHP app, it works on cheap shared hosting plans ($3–5/month on Namecheap, DreamHost, etc.) that don’t support Docker. This is actually an advantage for non-technical users who already have cPanel hosting — they can install Piwigo without ever touching a terminal.

Realistic time estimates:

• On a shared hosting account with cPanel: 30–60 minutes using NetInstall
• On a fresh VPS with LAMP/LEMP stack: 1–2 hours including web server configuration
• For someone who has never configured PHP hosting: a full afternoon

The SaaSHub analysis [3] is direct about the downside: “Setting up and maintaining Piwigo can be complex, particularly for users without technical expertise” and “there is a learning curve associated with effectively using and customizing Piwigo.”

---

Pros and cons

Pros

• 23 years of continuous development. In open-source software, longevity is a feature. Projects started in 2002 and still shipping in 2026 have survived the death of their competitors [website][4].
• Genuine organization support. Multi-level user groups, album-level permissions, and password-protected access aren’t afterthoughts — they’re core features built for teams [website][4].
• 200+ plugins. Real extensibility: batch operations, watermarking, anti-spam, comments, download controls, social sharing. Not all quality is equal (community-contributed), but the selection is wide [website][2].
• Runs on cheap shared hosting. No Docker, no Kubernetes, no VPS required — a $3/month shared host with PHP and MySQL is enough [README][4].
• Cloud hosting option in France. For European users who want managed hosting with GDPR-relevant data location but don’t want to DIY [4].
• High-volume handling. Explicitly designed for hundreds of thousands of photos, not just a personal library [website].
• GPL-2.0 license. Full open source — fork it, modify it, run it without vendor lock-in [merged profile].
• Active maintenance. Version 16.3.0 with security fixes and Docker updates shipped three weeks before this review [website].

Cons

• Dated setup experience. FTP-based install, PHP dependency, no official first-class Docker Compose path. Feels like 2010 compared to Immich’s one-command Docker setup [README][3].
• No AI photo features. No face recognition, no object/scene detection, no smart albums, no duplicate detection. Google Photos has spoiled users on these [4].
• UI is functional but not modern. The public-facing gallery and admin interface work, but they don’t look like a 2026 product. Multiple plugin themes exist to address this, but they require configuration [3][4].
• Plugin quality is uneven. Because many plugins are community-contributed, maintenance and compatibility vary. A plugin that worked on Piwigo 12 may not work on 16 [3].
• Mobile apps are basic. Upload and browse work, but there’s no automatic background sync comparable to Google Photos or iCloud [4].
• Performance depends heavily on hosting. The SaaSHub analysis [3] flags this explicitly: “Depending on the hosting environment and the size of the gallery, users might experience performance issues such as slow loading times.”
• No built-in video transcoding. Video support exists but Piwigo doesn’t transcode — you’re serving the original file, which can be slow or incompatible depending on format [4].

---

Who should use this / who shouldn’t

Use Piwigo if:

• You run an organization (tourism office, manufacturer, agency) that needs controlled photo sharing with tiered access for different user groups.
• You’re a photographer with a large archive who wants a self-hosted gallery with fine-grained album permissions and plugin extensibility.
• You want to escape per-gigabyte Google or iCloud storage fees for a team that collectively holds hundreds of gigabytes of photos.
• You already have PHP shared hosting and want photo management without a full server migration.
• You value software longevity — you want something that will still run in 2030.
• GDPR compliance matters and you want data in France (cloud option) or on your own server.

Skip it (consider Immich instead) if:

• You want Google Photos-style AI features: face detection, smart search, “remember this day” notifications, and automatic duplicate grouping.
• You want a modern Docker-first self-hosted experience with active GitHub momentum (Immich has 57K+ stars).
• Your primary use case is personal photo backup from a phone, not library management.

Skip it (consider Nextcloud Photos instead) if:

• You’re already running Nextcloud and want photo management as part of a broader file sync and collaboration suite.
• You want automatic photo backup from mobile with the same platform handling files, calendar, and contacts.

Skip it (stay on Google Photos) if:

• You have fewer than 15GB of photos and the free tier covers you.
• You need the AI-powered search and it genuinely saves you time daily.
• You have no technical resource to help with server setup.

Skip it (consider Chevereto or SmugMug instead) if:

• You want to build a public photo hosting service for clients — Chevereto is purpose-built for this, Piwigo is built for controlled library management [2].

---

Alternatives worth considering

• Immich — the current momentum leader in self-hosted photo management. Docker-first, Google Photos-inspired UI, face recognition, mobile backup app with background sync. 57K+ GitHub stars. If you want the modern experience, start here. Tradeoff: much newer (2021), less organizational permission depth than Piwigo.
• PhotoPrism — AI-powered photo indexing with TensorFlow-based face and object recognition. Docker-based, strong search. More personal library focus than organizational. Commercial licensing for some features.
• Nextcloud Photos — photo management as part of the broader Nextcloud ecosystem. Best if you want file sync + photos + collaboration in one stack. Weaker standalone gallery experience.
• Lychee — lightweight, clean open-source photo management. Simpler than Piwigo with fewer organizational features [2].
• Zenphoto — the closest peer to Piwigo in age and approach. CMS-focused, with blog and custom pages. Better for photographer portfolios, worse for organizational photo libraries [1].
• Google Photos — the incumbent. Best AI features, worst data sovereignty. Free up to 15GB.
• Chevereto — image hosting platform designed for public sharing, not private organizational libraries. Freemium [2].

For the non-technical founder escaping cloud storage fees for a team, the realistic decision is Piwigo vs Immich. Pick Piwigo if organizational permission depth and plugin extensibility matter, or if you need shared hosting compatibility. Pick Immich if you want the modern experience and have Docker.

---

Bottom line

Piwigo is not the flashiest tool in this category, and it doesn’t try to be. It is a stable, mature, GPL-2.0 photo management platform that has outlasted the majority of its competitors by doing the fundamentals well: album hierarchy, permissions, batch operations, plugins, and multi-user access control. The 23-year history isn’t a liability — it’s the product. Organizations that need controlled photo sharing without per-gigabyte SaaS fees, photographers with large archives who want server-side control, and anyone who’s been burned by a tool going unmaintained will find Piwigo’s track record reassuring.

The honest trade-offs: the setup is more manual than modern Docker-first tools, the UI hasn’t kept pace with 2026 design standards, and there are no AI photo features. If you came expecting the Google Photos experience on your own server, look at Immich instead. If you came expecting a reliable, extensible organizational photo library that you fully control, Piwigo is exactly what it claims to be.

If the server setup is the blocker, that’s precisely the kind of one-time deployment that upready.dev handles for clients.

---

Sources

1. SourceForge — Piwigo Reviews (user reviews and alternatives). https://sourceforge.net/software/product/Piwigo/
2. Alternative.me — 5 Best Piwigo Alternatives: Reviews, Features, Pros & Cons. https://alternative.me/piwigo
3. SaaSHub — Piwigo.org VS phpGraphy: compare differences & reviews. https://www.saashub.com/compare-piwigo-org-vs-phpgraphy
4. Ankush Das, It’s FOSS — “Piwigo: An Open-Source Google Photos Alternative That You Can Self-Host” (Mar 9, 2022). https://itsfoss.com/piwigo/

Primary sources:

• GitHub repository and README: https://github.com/piwigo/piwigo (3,756 stars, GPL-2.0)
• Official website: https://piwigo.org
• Cloud hosting: https://piwigo.com