Introducing a new way to review your PRs.

Read the announcement

immich-app / immich

High performance self-hosted photo and video management solution.

View on GitHub

21 documents · Updated Oct 19, 2026

docs / web-application-experience

Web application experience

The web application is a client-side SvelteKit app for browsing, managing, and sharing a photo library. It joins server data with local state, live server events, and browser media features so one shared shell can support sign-in, library work, administration, and media viewing. The related mobile system is described in Mobile application architecture.

Application startup

The startup path prepares the browser app before a route renders. It connects the generated SDK to SvelteKit's fetch function, loads language and server settings, restores the signed-in user when an auth cookie is present, and then loads server feature flags when maintenance mode is off. SvelteKit runs this path on the client because the app disables server-side rendering.

The startup sequence also enables the command palette and starts language tracking. The root layout then emits AppInit, which lets managers load browser capabilities such as supported upload types and cast destinations. It provides the query, tooltip, translation, upload, download, and media-control context that all routes use, and it keeps navigation feedback separate from route content.

flowchart TD
    A[Browser opens app] --> B[Root layout load]
    B --> C[Configure SDK fetch]
    C --> D[Load language]
    D --> E[Load server config]
    E --> F[Load auth user and preferences]
    F --> G{Maintenance mode?}
    G -- No --> H[Load feature flags]
    G -- Yes --> I[Use maintenance route]
    H --> J[Enable command palette]
    I --> J
    J --> K[Emit AppInit]
    K --> L[Render route shell]

References: web/…/+layout.ts• L9-34 web/…/server.ts• L10-24 web/…/+layout.svelte• L82-179

Route layout

The route tree separates shared application behavior from the main user, authentication, administration, and maintenance experiences. The Route helper is the common vocabulary for navigation, so pages can preserve route parameters and keep links aligned with the route tree.

The home route chooses the first user destination. Maintenance takes precedence, an authenticated user goes to the photo timeline, an initialized server goes to login, and an uninitialized server stays on the welcome page. The root layout adds shared error handling, metadata, navigation feedback, panels, command actions, query access, and the live connection around every route. It also changes the live connection as authentication, maintenance, or restart state changes, so route content and server state remain aligned.

Route areaUser-facing role
AuthenticationRegistration, login, password change, onboarding, and session lock flows
UserPhotos, albums, search, people, memories, sharing, utilities, settings, and workflows
AdministrationUsers, libraries, queues, system settings, maintenance, and server status
MaintenanceRestore and server maintenance while normal library access is paused
Shared linksLimited media views for visitors outside the normal signed-in flow

References: web/…/+page.ts• L9-44 web/…/+layout.svelte• L234-273 web/…/route.ts• L41-151

Page shells

Page shells give route groups a consistent frame while leaving each page to supply its own content. Authentication pages use a centered card with optional branding and backdrop. User pages combine the navigation bar, responsive library sidebar, scroll area, page header, and context actions. Administration pages use the same top bar with an app-shell sidebar and breadcrumb actions.

These shells also define the main responsive boundary. Wide screens expose side navigation and header actions, while narrow screens move actions into menus and collapse the sidebar behind the menu button. The sidebar state follows the current screen size and can be toggled only when the layout has room to hide it.

References: web/…/AuthPageLayout.svelte• L14-41 web/…/UserPageLayout.svelte• L49-107 web/…/AdminPageLayout.svelte• L22-46 web/…/sidebar.svelte.ts• L3-19

Client services and stores

Client services turn a user action into a server request and a visible result. They use the generated SDK for API calls, apply permission and feature checks, show translated errors or success messages, and emit domain events when other parts of the app must refresh. The service layer keeps route components focused on presenting state and collecting input.

The asset service also provides the shared action definitions for single assets and selected asset groups. These definitions connect permissions, feature settings, keyboard shortcuts, menus, dialogs, downloads, and server jobs. This keeps actions such as sharing, tagging, rating, and album changes consistent across timeline controls, menus, command entries, and viewer surfaces.

Trash actions extend the same service pattern to the asset lifecycle. They require confirmation before restoring all items or permanently emptying the trash, then report the server result through a translated notification.

The same action model supports administration. Library actions cover discovery, creation, editing, folder and exclusion rules, scanning, and deletion. System configuration actions support copy, JSON export, and conditional import, while user administration actions cover account changes and protected recovery operations. These services keep destructive or privileged work behind the right confirmation and access rules.

The stores and managers hold state that must outlive one component or coordinate several pages. They cover identity, user preferences, uploads, notifications, sidebar state, feature flags, server settings, timeline data, and live connection status. A shared event manager links these state owners without requiring every component to know every other component.

Client concernShared responsibility
Server and identity stateKeep server settings, feature flags, current user, and preferences ready for route guards and UI checks
User choicesPersist language, locale, map view, album view, and media playback choices in the browser
Work in progressTrack upload items, progress, duplicates, errors, and remaining work for the upload panel
Live updatesReceive asset, person, notification, release, session, and maintenance events through the socket connection
Domain refreshReconcile local views after album, asset, person, user, system setting, library, or workflow changes
Person accessShare recognized people with selected users or a wider user group and keep access changes visible through domain events
Recent activityClear cached recent albums after album changes and clear interaction state on logout

References: web/…/asset.service.ts• L63-139 web/…/asset.service.ts• L143-390 web/…/asset.service.ts• L393-554 web/…/album.service.ts• L46-161 web/…/person.service.ts• L27-78 web/…/person-user.service.ts• L19-142 web/…/trash.service.ts• L8-56 web/…/library.service.ts• L16-166 web/…/system-config.service.ts• L9-66 web/…/user-admin.service.ts• L26-134 web/…/upload.ts• L4-25 web/…/preferences.store.ts• L6-16 web/…/sidebar.svelte.ts• L3-19 web/…/user.svelte.ts• L4-28 web/…/event-manager.svelte.ts• L23-103

Authentication state

Authentication state is the shared gate for signed-in behavior. The auth manager checks for the browser auth cookie, loads the current user and preferences, and exposes an authenticated state used by navigation, services, and the socket connection. It also marks shared-link routes separately, so public viewing can use link state without treating the visitor as a signed-in user. A session deletion event sends the browser to logout, while logout clears the local identity before navigation.

The server configuration and feature flag managers sit beside auth state. They refresh when system configuration changes, so the same server event can change which navigation items and actions the user sees without a full page reload.

References: web/…/auth-manager.svelte.ts• L16-83 web/…/auth-manager.svelte.ts• L93-138 web/…/server-config-manager.svelte.ts• L4-27 web/…/feature-flags-manager.svelte.ts• L4-27 web/…/SharedLinkPage.svelte• L30-64

Live connection

The live connection carries server events that make the UI react to work completed elsewhere. The root layout opens it for an authenticated user, a restart state, or a maintenance route and closes it for an unauthenticated normal route. Events update shared state or become domain events for pages such as the timeline, people view, notifications, configuration, administration, and release notices.

Server restart and maintenance events are part of this same path. Configuration changes invalidate the shared configuration query, while session deletion drives logout and asset events drive domain refresh. The app can show a restart modal, redirect to maintenance, or reload after the server returns to the expected mode.

References: web/…/websocket.ts• L29-107 web/…/websocket.ts• L109-148 web/…/+layout.svelte• L203-231 web/…/event-manager.svelte.ts• L23-103

UI component architecture

The UI is built from route pages, page shells, shared feature components, and the shared @immich/ui package. Route pages compose these parts and own page-specific data flow. Shared components provide common navigation, search, sidebars, media viewers, settings controls, menus, and feedback surfaces.

The application uses actions and modals to keep user operations consistent across pages. Services create action descriptions with permission and feature rules, while shared UI components render those actions as buttons, menus, command entries, or dialogs. This lets desktop and mobile layouts expose the same operation through different controls. The asset viewer uses this shared action contract for media actions, including preference-gated ratings and owner-only operations, instead of giving each control its own permission path.

The main signed-in shell illustrates the composition: the navigation bar provides search, upload, theme, notices, cast, and account entry points; the account panel adds settings, administration for administrators, support, and sign-out; the sidebar exposes library areas that match the user's preferences and server flags; the page body renders the active route. The sidebar's lower area also gives users server connection, version, release, and storage context.

References: web/…/NavigationBar.svelte• L38-181 web/…/AccountInfoPanel.svelte• L26-116 web/…/UserSidebar.svelte• L42-119 web/…/ServerStatus.svelte• L14-96 web/…/StorageSpace.svelte• L10-55 web/…/ServerStatisticsCard.svelte• L6-58 web/…/app.service.ts• L7-19 web/…/asset.service.ts• L63-139 web/…/asset.service.ts• L143-390 web/…/app.css• L1-40

Media and library surfaces

Library screens share a timeline and asset-viewer model so browsing, search, albums, memories, people, and shared links can open media with related actions. The timeline presents assets in date groups and supports selection, keyboard navigation, scrubbing, deep links, and an overlay viewer. The gallery viewer provides a similar asset grid for other library surfaces while keeping selection and viewer navigation in the same client model.

The places view adds a location-based library surface. It keeps assets that have a city, lets the user search by city, and can present the results as one list or as country groups. Group headers expose collapse state that follows the saved places view settings, while each place links into the normal city search flow.

The photo viewer adds the direct media experience on top of that model. It supports zoom, swipe navigation, slideshow control, image copy, casting, face labels, face highlighting, face editing, and OCR overlays while the displayed image remains the source for those overlays.

The timeline viewer keeps the open asset tied to the timeline around it. When an action removes the current asset, it updates the timeline first, moves to a nearby asset when possible, and closes the viewer when no nearby asset remains. Upload and asset-update events can refresh the open asset, while restore actions can put it back into the timeline and viewer.

Asset and album services provide the common operations for sharing, downloading, editing, tagging, favoriting, adding to albums, and starting server jobs. The detailed library flows are covered in Web library workflows.

Album views combine owned and shared albums with search, filtering, grouping, sorting, and either card or list presentation. They also apply album events so an update, deletion, or new shared link is reflected without rebuilding the whole page. The web app also exposes workflows as a user-facing route area. Workflow pages use the same service, event, and action patterns while presenting workflow-specific editing and execution controls.

Thumbnails are the common entry point for media selection and preview. They adapt hover behavior to the device, support keyboard and long-press selection, show media-specific playback or state markers, and keep a low-cost placeholder visible while media loads. Person thumbnails also show compact status indicators for favorite people and people shared with the current user, so the same relationship state is visible in both the people list and the explore view. The selection control gives clear hover feedback without changing the shared selection contract. Shared-link views use the same media surfaces but change the available upload, download, selection, and deletion actions to match link permissions. SharedLinkPage handles the public boundary: it asks for a password when needed, selects the album or individual viewer after access is granted, and clears the link state when the page closes.

References: web/…/Timeline.svelte• L88-122 web/…/Timeline.svelte• L200-257 web/…/Timeline.svelte• L578-714 web/…/TimelineAssetViewer.svelte• L42-87 web/…/TimelineAssetViewer.svelte• L118-183 web/…/PhotoViewer.svelte• L41-56 web/…/PhotoViewer.svelte• L91-152 web/…/PhotoViewer.svelte• L175-204 web/…/GalleryViewer.svelte• L66-119 web/…/GalleryViewer.svelte• L121-205 web/…/GalleryViewer.svelte• L382-397 web/…/asset.service.ts• L63-139 web/…/asset.service.ts• L143-390 web/…/album.service.ts• L54-163 web/…/AlbumsList.svelte• L117-196 web/…/Thumbnail.svelte• L74-111 web/…/Thumbnail.svelte• L113-193 web/…/Thumbnail.svelte• L385-413 web/…/PersonIndicator.svelte• L1-26 web/…/PeopleCard.svelte• L35-48 web/…/+page.svelte• L70-99 web/…/PlacesList.svelte• L31-87 web/…/PlacesCardGroup.svelte• L16-59 web/…/places-utils.ts• L10-63 web/…/SharedLinkPage.svelte• L32-109 web/…/IndividualSharedViewer.svelte• L46-145 web/…/route.ts• L41-147

Memory cards

Memory cards turn a memory into a compact link with an image, title, and saved state. Birthday memories add a small celebratory effect on hover, while the effect respects the browser's reduced-motion preference so it does not change the basic memory navigation path.

References: web/…/MemoryCard.svelte• L12-28 web/…/MemoryCard.svelte• L37-75 web/…/BirthdayConfetti.svelte• L3-21

Administration surfaces

Administration uses a separate shell because its navigation and actions target server-wide state. Its pages manage users, external libraries, queues, system settings, maintenance, and server status. Library screens let administrators scan libraries and manage their folders and exclusion rules. System settings use a shared save and reset pattern, can preview storage templates, and disable database editing when a configuration file owns the value. Queue cards show whether a queue is paused or active and expose controls for clearing, pausing, resuming, or starting queue work. Server statistics cards present loading-safe summary values, while the sidebar exposes connection, version, release, and storage state. The administration and authentication details are covered in Web administration and authentication.

References: web/…/AdminPageLayout.svelte• L22-46 web/…/library.service.ts• L16-166 web/…/system-config.service.ts• L9-66 web/…/user-admin.service.ts• L26-134 web/…/StorageTemplateSettings.svelte• L41-58 web/…/StorageTemplateSettings.svelte• L105-159 web/…/SystemConfigButtonRow.svelte• L19-59 web/…/ServerStatisticsCard.svelte• L19-40 web/…/route.ts• L63-73 web/…/route.ts• L120-151

Browser capabilities

The app uses browser APIs to make media work efficient and to adapt the experience to the device. These capabilities are optional where browser support varies. The app checks support before it uses a feature and keeps core navigation and library access in the normal API path.

CapabilityUser-facing purpose
Service workerShare and cancel in-flight thumbnail and original-image requests, with request de-duplication for repeated image loads
Media capabilitiesChoose video levels that the browser can decode smoothly and with lower power use
Screen wake lockKeep the screen awake during supported media activity and reacquire it when the page becomes visible
Clipboard and file APIsCopy data, select uploads, import configuration, and download media or JSON
Cast APIsDiscover a supported cast target and control remote playback through a short-lived media session
Local storage and media queriesKeep display choices across visits and adapt navigation and theme to the device

References: web/…/index.ts• L9-37 web/…/request.ts• L19-69 web/…/media-capabilities-manager.svelte.ts• L10-91 web/…/wakelock.svelte.ts• L4-51 web/…/cast-manager.svelte.ts• L40-149 web/…/PhotoViewer.svelte• L91-152 web/…/BirthdayConfetti.svelte• L15-21

Theme and language

Theme selection starts before the Svelte app renders so the browser does not show the wrong theme during startup. The root layout maps application strings and media controls to the selected locale. The language manager also sets the document direction for right-to-left languages.

Language and view preferences persist in local storage. A missing or unsupported browser preference falls back to an available application language, and stored view settings keep the user's chosen library presentation between visits.

The global stylesheet defines the shared light and dark color tokens, fonts, responsive breakpoints, form styles, scrollbar behavior, and media-viewer background. Components use these shared values so a theme change affects the full shell rather than one route.

References: web/…/app.html• L19-30 web/…/+layout.svelte• L81-165 web/…/language-manager.svelte.ts• L15-34 web/…/preferences.store.ts• L6-16 web/…/persisted.ts• L64-93 web/…/app.css• L1-40 web/…/app.css• L73-176

Media delivery

The service worker handles same-origin asset image requests for thumbnails and originals. It shares one pending fetch among callers and can abort a request when the viewer no longer needs it. The page sends cancellation messages only in a secure context with service-worker support, so unsupported browsers keep the normal fetch behavior.

The client utility layer selects a preview, original, or full-size asset URL from the asset type, animation state, user preference, and shared-link permissions. This keeps media display efficient while preventing restricted shared links from receiving an original asset. It also provides download and upload request paths with progress and cancellation support.

People overlays use the same media path. Face coordinates from the server are scaled to the displayed image, and the browser can crop a face region into an image for face-focused views.

Video playback also uses browser media capability checks and optional cast support. The result is a media experience that can favor a browser-efficient stream without making the route depend on one browser vendor.

References: web/…/index.ts• L21-36 web/…/request.ts• L19-69 web/…/sw-messaging.ts• L1-11 web/…/utils.ts• L192-258 web/…/utils.ts• L284-328 web/…/people-utils.ts• L8-78 web/…/media-capabilities-manager.svelte.ts• L37-82 web/…/PhotoViewer.svelte• L228-300

Change checklist

When these files or sections are changed, remember to consider these:

  • Changes to startup order must preserve the dependency between server config, auth state, feature flags, language, query context, and route redirects.
  • Changes to socket event names or payloads must stay aligned with the event manager and the stores or managers that consume those events.
  • Changes to route paths must update the Route helper and any redirect or same-origin continuation logic that builds links.
  • Changes to feature flags or user preferences must account for both the sidebar visibility rules and the action visibility rules.
  • Changes to service-generated asset actions must keep permission checks, command-palette entries, viewer menus, timeline controls, and keyboard shortcuts aligned.
  • Changes to person sharing must preserve bulk upsert and removal behavior as well as the event names and payloads used to refresh person access views.
  • Changes to person thumbnail indicators must keep favorite and shared-person state aligned across the people list and explore surfaces.
  • Changes to trash actions must preserve confirmation, server result counts, and the translated feedback for both restore-all and permanent deletion.
  • Changes to service-worker asset matching must stay aligned with image cancellation messages and the media URL shapes used by viewers.
  • Changes to shared page shells must preserve both desktop controls and their compact mobile menu equivalents.
  • Changes to album or shared-link viewer state must preserve the difference between single-asset viewing and multi-asset selection.
  • Changes to asset URL rules must preserve the shared-link limits for original media and the preview or original choices for animated images and video.
  • Changes to face coordinate handling must keep server image dimensions aligned with the displayed image dimensions before overlays or crops are created.
  • Changes to viewer asset actions must update the timeline state before navigation so removal, restore, upload, and live asset updates do not leave a stale open item.
  • Changes to memory effects must preserve the reduced-motion behavior and the link and saved-state behavior of memory cards.
  • Changes to global theme tokens or breakpoints must preserve the component styles that depend on the shared app.css contract.
  • Changes to timeline or gallery layout must preserve the link between loaded asset ranges, viewport windows, selection ranges, and viewer navigation.
  • Changes to places search or grouping must keep city filtering, country group IDs, saved collapse state, and the places controls aligned.
  • Changes to storage-template controls must keep preset values, custom previews, config-file locks, and save-on-close behavior aligned with the system configuration contract.
  • Changes to queue status badges must preserve the link between queue state and the badge's color and label, including dark and small-screen styles.
  • Changes to shared-link password handling must keep link state, viewer selection, page titles, and cleanup aligned across password-protected and open links.
  • Changes to administration actions must keep confirmation rules, self-user protections, configuration-file locks, and query invalidation aligned with server permissions.
  • Changes to recent-album interaction state must preserve its reset behavior for album events and logout.

Important failure modes

TriggerConsequenceGuard
Server config fails during startupRoutes cannot safely decide between normal and maintenance behaviorRoot load records the error and the root layout renders ErrorLayout instead of the route content
Auth user or preference load is stale after session deletionA signed-out browser can keep showing signed-in state or try to use protected servicesSessionDelete navigates to logout and the auth manager clears its user and preference state
A socket event contract changes without updating consumersTimeline, notifications, maintenance, or release state can stay stale with no page reload signalKeep socket event types, event-manager names, and consuming stores aligned
An action is exposed without its service permission ruleA user can see a control that the viewer or server must reject, or a valid action can disappear from one surfaceBuild viewer, menu, timeline, and command actions from the same service action definitions
Bulk tagging or person access changes omit their domain eventAsset or person views can show old state until a full reloadEmit and consume the matching asset or person events after successful service calls
Person bulk updates mix selected and removed users incorrectlyAccess can remain for a person or user that the bulk editor meant to removeKeep the upsert and removal sets separate and map each removal to the intended person-user pair
Person state indicators use different conditions across surfacesA person can appear favorite or shared in one view but not anotherRender both surfaces through PersonIndicator and derive its icons from the person response state
A restore-all or empty-trash request skips confirmationA user can restore or permanently delete the whole trash by mistakeShow the matching confirmation dialog before the server request
The current viewer asset is removed without updating the timeline firstThe viewer can show a removed asset or navigate to an invalid neighborUpdate the timeline, choose the next or previous asset, and close the viewer when no neighbor exists
A new viewer asset keeps the previous zoom or face stateOverlays or scale can belong to the prior imageReset zoom, visible-image readiness, and highlighted faces when the asset ID changes
Birthday effects ignore reduced-motion settingsA decorative interaction can cause unwanted motionPass reduced-motion handling to the confetti effect and keep the card usable without it
Browser lacks service-worker or wake-lock supportRequest cancellation or screen wake behavior is unavailableCapability checks make these features optional and keep the normal browser path active
A route or feature flag is changed in only one navigation layerA link can point to a hidden, invalid, or inaccessible pageTreat route helpers, sidebar rules, action rules, and redirect rules as one navigation contract
A shared-link viewer applies signed-in actions to a visitorA visitor can receive controls that the link does not allowDerive upload, download, selection, and deletion controls from shared-link permissions
Shared-link password state is not cleared after leaving the pageA later route can reuse stale public-link data or show the wrong viewerClear shared-link state on destroy and update the viewer only after successful link login
Shared-link permission rules are ignored when building an asset URLA visitor can receive original media or metadata that the link does not allowApply shared-link download and metadata limits before selecting the media size
Server face coordinates are used without image-size scalingFace labels or crops appear in the wrong place or sizeConvert normalized face bounds to the current image dimensions before rendering or cropping
A timeline or gallery window loses its loaded-range or scroll state during viewer navigationThe user returns to the wrong place or sees missing assets around the selected itemKeep viewport state, asset loading, and viewer route changes under the shared timeline or gallery navigation flow
Places search filters by a different field than the place cards displayA user can search for a visible city and get no resultNormalize the same city value for filtering and display, and keep the result count tied to the filtered list
Places group IDs do not match the saved collapse stateA group's open or closed state can move to another country or reset unexpectedlyUse stable country names as group IDs and update the control list from the current grouped result
A storage template is edited while file-based configuration controls the valueThe screen can suggest a change that the server will not acceptDisable the setting when the config-file feature flag is active and use the shared system-config save path
A configuration import bypasses the shared update pathThe server may reject invalid data or other views may keep stale configurationRoute imports through the system-config mutation and let the shared query update path handle the result
An administrator can reset or delete a protected user without the current-user guardThe administrator can lock out the wrong account or expose an invalid recovery actionHide self-delete and self-password-reset actions and require the matching confirmation flow
A queue badge does not match the queue stateAn administrator can read an active queue as paused or miss that it is pausedDerive the badge from the queue's paused state and active count, and keep its success and warning styles readable in both themes
Storage or server data is not ready when a summary card rendersThe page can show a false zero instead of a value that is still loadingKeep loading values distinct from zero and render the loading-safe card state until data arrives
Recent album state is not cleared after an album event or logoutThe sidebar can show albums that no longer exist or belong to the prior sessionReset recent interaction state from the matching domain events

Key files

FileWhy to read it
web/…/+layout.tsDefines client startup, maintenance redirects, and shared layout data
web/…/+layout.svelteDefines the global shell, navigation feedback, localization hooks, panels, query context, and socket lifecycle
web/…/server.tsShows the order for SDK, language, server, auth, and feature initialization
web/…/route.tsDefines the application's navigation vocabulary and route parameter rules
web/…/UserPageLayout.svelteShows the signed-in page frame and responsive action behavior
web/…/AdminPageLayout.svelteShows the administration frame and server-management navigation
web/…/auth-manager.svelte.tsDefines shared identity, shared-link context, and preference state for protected UI
web/…/websocket.tsDefines live server events and their connection state
web/…/event-manager.svelte.tsDefines the cross-feature event contract
web/…/user.svelte.tsShows how small shared interaction state follows domain events and logout
web/…/NavigationBar.svelteShows the main user controls and responsive navigation entry points
web/…/AccountInfoPanel.svelteShows account, support, administration, and sign-out entry points
web/…/UserSidebar.svelteShows how library navigation follows feature flags and user preferences
web/…/ServerStatus.svelteShows server connection, version, and release feedback in the shared shell
web/…/StorageSpace.svelteShows quota-aware storage feedback in the shared shell
web/…/sidebar.svelte.tsShows how sidebar visibility follows the responsive layout
web/…/asset.service.tsShows how shared asset actions enforce access rules and update the rest of the client
web/…/trash.service.tsShows how restore-all and permanent trash deletion become confirmed user actions
web/…/person-user.service.tsShows how person access supports individual and bulk sharing changes
web/…/library.service.tsShows how administration actions manage libraries and their scan inputs
web/…/system-config.service.tsShows how configuration copy, export, and import use shared actions
web/…/user-admin.service.tsShows protected administrator actions for users and account recovery
web/…/Timeline.svelteShows the date-based library surface, viewport loading, selection, scrubbing, and viewer routing
web/…/TimelineAssetViewer.svelteShows how the open viewer stays in sync with timeline removal, restore, upload, and live updates
web/…/PhotoViewer.svelteShows the photo viewer's zoom, cast, copy, face, OCR, and slideshow interactions
web/…/GalleryViewer.svelteShows the shared gallery grid, selection behavior, viewport window, and viewer overlay
web/…/AlbumsList.svelteShows how album data becomes searchable, grouped, sorted, and live-updated views
web/…/PlacesList.svelteShows how place results become searchable and grouped by the user's view setting
web/…/PlacesCardGroup.svelteShows place group collapse behavior and links from place cards to city search
web/…/places-utils.tsDefines the saved collapse state for place groups
web/…/Thumbnail.svelteShows the shared media tile behavior for selection, preview, playback, and loading
web/…/PersonIndicator.svelteShows the shared favorite and shared-person status markers used on person thumbnails
web/…/PeopleCard.svelteShows person indicators in the full people surface
web/…/+page.svelteShows person indicators in the explore summary surface
web/…/AssetViewerNavBar.svelteShows how the viewer presents shared service actions across controls and menus
web/…/ActivityViewer.svelteShows the shared viewer activity surface for comments and reactions
web/…/SharedLinkPage.svelteShows the password boundary and viewer choice for public links
web/…/IndividualSharedViewer.svelteShows how shared-link permissions shape single-asset and gallery experiences
web/…/MemoryCard.svelteShows how memories become links with saved state and birthday feedback
web/…/BirthdayConfetti.svelteShows the reduced-motion-safe birthday effect used by memory cards
web/…/QueueCard.svelteShows queue status, counts, and administrator controls
web/…/QueueCardBadge.svelteShows the shared queue status badge and its theme-aware status styles
web/…/StorageTemplateSettings.svelteShows how administration presents storage path choices, previews, and system-config saves
web/…/SystemConfigButtonRow.svelteShows shared reset, default, and save behavior for system settings
web/…/ServerStatisticsCard.svelteShows the loading-safe summary card used for server statistics
web/…/index.tsDefines browser-side asset request handling
web/…/media-capabilities-manager.svelte.tsDefines browser-aware media quality selection
web/…/utils.tsDefines shared client rules for asset URLs, downloads, uploads, OAuth, and user-facing helpers
web/…/people-utils.tsDefines face overlay geometry and browser face-image crops
web/…/app.cssDefines shared theme tokens, fonts, breakpoints, and base browser presentation