English
Photoview Hosting
Browse and share media libraries through fast galleries and generated thumbnails.
No setup fees-
One click deploy -
2 GB RAM Memory needed -
25 GB Disk Space Needed -
From 5 € Price
Official links
Photoview’s official links and original website
Photoview Website
More
Tech
- Docker image
- photoview/photoview:2
- Default port
- 80
- Database
- mariadb
How Photoview works
Photoview scans configured media directories, reads image and video metadata, and builds a database-backed catalogue without requiring the operator to reorganise everything inside the web application. The interface presents the indexed collection through chronological views, folders or albums, search, and location-based browsing when suitable metadata is available.
Background processing generates thumbnails and prepares information used for maps and recognised-person grouping. The original media directory remains the source of the library, so file naming, folder structure, permissions, and the quality of embedded metadata influence what users see after a scan.
Key Photoview features
Timeline browsing provides a chronological route through a large collection, while directory-based albums preserve an existing organisational structure. Map views use available coordinates, and face-recognition processing can group likely matches so an operator can review people across different events.
Public sharing exposes selected albums or media without opening the complete library. Search and metadata filters make it easier to locate material, but automatic recognition is probabilistic: names, face groups, and locations should be reviewed when accuracy matters.
Photoview vs Google Photos
Photoview is a self-hosted gallery layer that indexes media stored in directories chosen by the operator. Google Photos is a provider-managed cloud service with automatic mobile backup, Google Account storage, consumer applications, and access across signed-in devices.
Google Photos may suit households that want phones to upload directly into a vendor-operated library. Photoview is more attractive when existing folders should remain the source of truth and the owner wants a private browsing interface, although the operator must manage uploads, storage, indexing, and recognition workloads.
Who uses Photoview
Families use Photoview to browse a shared archive copied from cameras and phones. Photographers can expose selected albums to clients or collaborators, while home-server users add a modern interface to media already arranged in a directory tree.
It is not a replacement for an independent backup or a managed mobile-upload ecosystem. Large imports can trigger sustained thumbnail and recognition work, and an incorrect folder mount or permission can leave part of the library unseen until the configuration is corrected.
Self-hosting Photoview: requirements and cost
Storage volume is the long-term constraint, while scanning, thumbnail generation, metadata extraction, video handling, and face recognition create processor and memory demand. MariaDB stores users, albums, media metadata, shares, and recognition state. AvaHost includes the database container but leaves it unmanaged, and the confirmed mapping adds database headroom above the application minimum.
The final recommendation is Plan 3 at €10 with 50 GB for the initial Photoview library; Plan 4 supplies 100 GB for a larger archive. AvaHost includes one-click deployment, a custom gallery domain, automated HTTPS, automatic application updates, and scheduled backups. Maintain a separate copy of original media rather than relying on the browsing installation as the sole archive.
F.A.Q
Photoview begins at €10 on Plan 3 after adding capacity for the MariaDB service. The plan includes 50 GB for originals, previews, thumbnails, and application data. Library size, scan frequency, video content, face processing, and concurrent viewers are the main indicators for moving to a larger configuration.
Start with the size of the mounted media directory, then leave room for new imports, thumbnails, previews, database records, and processing output. Photoview is storage-driven. Plan 3 provides 50 GB, while Plan 4 provides 100 GB for a larger collection. Preserve original files in an independent backup as well.
MariaDB is created with the application and connected to Photoview during deployment, but it remains unmanaged. The database contains accounts, indexed metadata, album relationships, shares, and recognition state, while originals live in persistent media storage. Treat both areas as one service when planning rescans, updates, moves, or recovery.
The hosted gallery can use a custom domain with automated HTTPS once DNS points to the service. Set the final address before distributing public shares. After connection, verify sign-in, thumbnails, maps, album links, media playback, and any external references that were created using the previous application hostname.