PhotoPrism Hosting

Organize, search, browse, and share private photo collections with intelligent indexing.

Order now No setup fees
  • One click deploy
  • 4 GB RAM Memory needed
  • 50 GB Disk Space Needed
  • From 10 € Price

Tech

Docker image
photoprism/photoprism:latest
Default port
2342
Database
mariadb

How PhotoPrism works

PhotoPrism reads original photos and videos from its library, indexes available metadata, and creates the derived information needed for browsing. The resulting catalogue can be explored by date, folder, album, camera, location, colour, labels, and other filters. Users can keep the originals in an organised file structure while the application provides a visual layer over them.

Indexing is the key background process. New or changed originals must be scanned before they appear correctly in the catalogue, and a complete rescan can revisit existing files. The application can generate previews, classify images, identify faces, and build search data, which is why the first pass over a large archive may be much heavier than routine browsing.

Key PhotoPrism features

Search filters can combine properties such as year, camera, country, colour, labels, file name, and recognised people. Albums provide a curated view separate from the underlying folders, while labels and metadata help users rediscover media that would otherwise remain buried in a large archive.

Face recognition groups similar faces so people can be organised, and the browsing interface includes views for moments, places, calendar periods, labels, and other catalogue perspectives. Sharing links can expose selected content when sharing is enabled, without opening the entire private library.

PhotoPrism vs Google Photos

PhotoPrism runs against media stored on infrastructure chosen by the owner and gives that owner control of indexing and catalogue settings. Google Photos is a managed cloud photo service tied to Google Accounts and storage shared with services such as Drive and Gmail. Both help search and share photos, but they place storage and operations under different control.

Google Photos may suit users who want automatic mobile backup, access across signed-in devices, provider-managed storage, and minimal administration. PhotoPrism suits people who already maintain a photo archive and want a self-hosted browser over it. The trade-off is responsibility for capacity, indexing time, backups, and application maintenance.

Who uses PhotoPrism

Photographers use PhotoPrism to browse a private archive by camera, date, place, or label. Families can organise shared collections, and collectors can place many years of folders behind a searchable web interface. It is also useful for reviewing an existing library without first importing every image into a proprietary cloud account.

The application is less suitable for someone expecting a storage plan to include a complete consumer photo service with bundled mobile cloud capacity. Large RAW collections and video archives can require substantially more disk than the minimum hosting plan.

Self-hosting PhotoPrism: requirements and cost

Storage is the lasting constraint, while indexing, previews, classification, face processing, and large searches create temporary compute demand. The catalogue deployment pairs PhotoPrism with MariaDB, so albums, labels, people, settings, and index records depend on the database while originals remain in the media volume. The recommended plan accounts for both PhotoPrism and its MariaDB container.

AvaHost maps PhotoPrism to Plan 4 at €20, and the software itself is free to run. Plan 4 provides 100 GB for the mapped minimum deployment; larger archives require additional capacity planning. One-click deployment provisions PhotoPrism and MariaDB, but the database remains unmanaged by AvaHost. PhotoPrism hosting includes automatic application updates, scheduled backups, custom-domain support, and automated HTTPS.

F.A.Q

  • PhotoPrism begins at €20 on Plan 4, which provides 100 GB for the mapped minimum deployment. This recommendation accounts for both PhotoPrism and its MariaDB container. Original photos, videos, previews, and index data can fill space quickly, so larger archives require additional capacity planning.

  • Plan 4 provides 100 GB for the mapped minimum deployment. Measure the original media first, then add room for previews, thumbnails, database growth, and future uploads. RAW files and video increase demand quickly. Keep an independent copy of originals outside PhotoPrism and review capacity before importing a substantial archive.

  • The one-click stack provisions MariaDB and connects it to PhotoPrism automatically. The database stores catalogue records, settings, albums, labels, people, and index information, while originals remain in the media volume. MariaDB is included but unmanaged by AvaHost, so database records and original files should be considered together during maintenance or recovery.

  • A custom domain with automated HTTPS can provide a stable address for the private gallery and selected share links. Changing that address later can affect saved links and integrations. Administrators should retest sign-in, browsing, indexing, uploads, and sharing after the final domain is attached.