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-library-workflows

Web library workflows

The web library is the browser workspace for turning stored media into useful user actions. It lets a user bring assets into the library, browse them in time-based views, inspect and change them, find them with filters, place them in albums, download them, and share them with other people.

This page focuses on the browser experience. See the web application experience page for the wider web product and web administration and authentication for access and admin context. See asset lifecycle and media processing for work after intake and asset organization and discovery for the data features that support search and grouping.

Library workspace

The library presents assets through several related views rather than one fixed page. The main photo timeline is the broad personal view. Search, albums, recently added assets, memories, explore, places, trash, and shared links narrow or change that view while keeping common viewing and selection patterns.

The browser uses route state to preserve the user’s place. A route can identify a view and an asset. A timeline query can also identify the asset position that should remain visible when the viewer closes.

Asset grid navigation

The asset grid is a time-ordered, scrollable view that loads month and day groups as the user moves through the library. A thumbnail click opens the asset viewer. Selection mode changes the same grid from navigation into a work surface for bulk actions. web/…/Timeline.svelte• L31-89, web/…/Timeline.svelte• L171-223

The route can point to a specific asset. When the page opens or the user returns from the viewer, the grid finds and scrolls to that asset. This makes browser history and direct links useful even for a large library. web/…/Timeline.svelte• L225-257

References: web/…/Timeline.svelte• L31-89 web/…/Timeline.svelte• L171-223 web/…/Timeline.svelte• L225-257

View routes

Each major library view supplies a different asset scope to the common grid or gallery:

The album route keeps normal viewing separate from asset-add and cover-selection modes. It disables normal asset routing while the user selects existing assets, clears the asset position when selection starts, and restores the previous grid position when the user returns to the album. web/…/+page.svelte• L104-151, web/…/+page.svelte• L341-358, web/…/+page.svelte• L568-593

References: web/…/+page.svelte• L39-40 web/…/+page.svelte• L92-113 web/…/+page.svelte• L220-239 web/…/+page.svelte• L104-151 web/…/+page.svelte• L341-358 web/…/+page.svelte• L568-593 web/…/+page.svelte• L23-50 web/…/PlacesList.svelte• L35-79

Asset intake

Browser upload flow

The upload flow starts from a file picker or an empty library view. The browser asks the server for supported image and video types, rejects unsupported files early, and places accepted files in a visible upload queue. The queue gives the user progress, duplicate counts, errors, and a way to keep working while uploads continue. web/…/upload-manager.svelte.ts• L6-31, web/…/file-uploader.ts• L28-109, web/…/UploadPanel.svelte• L36-50

For each accepted file, the browser checks for a known asset when the user is signed in. A new file is then sent to the asset intake endpoint. If the upload belongs to an album, the browser adds the resulting asset to that album after intake. This connects upload, duplicate handling, and organization without a separate user step. web/…/file-uploader.ts• L150-240

flowchart LR
  A[Choose files] --> B[Check supported types]
  B --> C[Show upload queue]
  C --> D{Known asset?}
  D -->|Yes| E[Mark duplicate]
  D -->|No| F[Send asset]
  F --> G{Album selected?}
  G -->|Yes| H[Add asset to album]
  G -->|No| I[Finish intake]
  E --> J[Show result]
  H --> J
  I --> J

References: web/…/upload-manager.svelte.ts• L6-31 web/…/file-uploader.ts• L28-109 web/…/file-uploader.ts• L150-253 web/…/UploadPanel.svelte• L36-50

Album upload flow

An album editor can upload from its add-assets view. The browser passes the album identity into the same upload flow, so the new asset appears in the album after upload. The album also supports adding existing library assets through a separate selection mode. web/…/album.service.ts• L122-143, web/…/+page.svelte• L568-583

The two paths serve different user goals. Upload adds a file that is not yet in the library. Asset selection links an existing library asset to the album. Both paths update the album view through album events, so the user does not need to reload the page. web/…/album.service.ts• L146-170, web/…/+page.svelte• L287-301

References: web/…/album.service.ts• L122-170 web/…/+page.svelte• L287-301 web/…/+page.svelte• L568-583

Asset viewing and management

Asset viewer

The asset viewer turns a selected thumbnail into a focused workspace for one asset. It supports previous and next navigation, stacked asset navigation, photo and video playback, metadata inspection, and an editor for eligible images. The viewer also exposes media-specific actions such as zoom, motion-photo playback, copying, slideshow playback, casting, and visual data overlays when the related data is available. web/…/AssetViewer.svelte• L222-304, web/…/PhotoViewer.svelte• L90-115, web/…/PhotoViewer.svelte• L176-297

The viewer’s navigation bar presents actions according to the asset, the current album, ownership, trash state, and whether the user is viewing a shared link. This keeps actions such as archive, restore, album placement, visibility changes, and processing jobs inside the access context that can perform them. web/…/AssetViewerNavBar.svelte• L59-81, web/…/AssetViewerNavBar.svelte• L120-175

The viewer is connected to the route through the timeline. The grid stays the source view, while the viewer is placed over it and keeps the grid position for return navigation. Before an action removes the current asset from that view, the browser moves to a neighboring asset or closes the viewer. Undo can restore the asset to the grid and reopen it. Upload and asset-update events can also refresh the asset that is currently open. web/…/TimelineAssetViewer.svelte• L49-87, web/…/TimelineAssetViewer.svelte• L99-167, web/…/TimelineAssetViewer.svelte• L169-183, web/…/Timeline.svelte• L710-714

References: web/…/AssetViewer.svelte• L222-304 web/…/PhotoViewer.svelte• L90-115 web/…/PhotoViewer.svelte• L176-297 web/…/AssetViewerNavBar.svelte• L59-81 web/…/AssetViewerNavBar.svelte• L120-175 web/…/TimelineAssetViewer.svelte• L49-87 web/…/TimelineAssetViewer.svelte• L99-183 web/…/Timeline.svelte• L710-714

Shared album activity

Shared albums can expose an activity panel beside the asset view. The panel groups comments and likes by time, lets permitted users remove reactions, and lets users add comments unless album activity is disabled. When it is opened without one asset selected, each reaction can link back to the asset that received it. web/…/ActivityViewer.svelte• L70-119, web/…/ActivityViewer.svelte• L140-224

The album page shows this panel only in a shared, signed-in album outside the focused viewer. It initializes shared activity for the album and closes the panel when activity is no longer available. The album owner can remove reactions, while a user can remove their own reaction. web/…/+page.svelte• L220-259, web/…/+page.svelte• L596-604, web/…/ActivityViewer.svelte• L121-137

References: web/…/ActivityViewer.svelte• L70-119 web/…/ActivityViewer.svelte• L121-224 web/…/+page.svelte• L220-259 web/…/+page.svelte• L596-604

Asset actions

Asset actions change the library record or create a new relation around it. The browser exposes actions such as favorite, archive, tag, album membership, metadata edits, visibility changes, sharing, and media refresh jobs. Availability depends on ownership, the current view, the asset state, and enabled product features. web/…/asset.service.ts• L124-218, web/…/asset.service.ts• L309-361

The same actions work on one asset in the viewer or on many selected assets in a grid. The main photo route also supports stack and live-photo linking for eligible selections. A linked live photo combines an image and its motion video, while unlinking restores both assets to the timeline. Bulk selection adds album, download, archive, delete, visibility, tag, stack, live-photo, and media-job operations while keeping ownership checks in place. web/…/+page.svelte• L42-70, web/…/+page.svelte• L115-166, web/…/+page.svelte• L343-392

Album selection adds album-specific controls to the same model. An editor can add or remove assets, set one selected asset as the cover, and apply permitted bulk changes without leaving the album. The album actions also expose keyboard shortcuts for common album changes, including removal when the user has permission. web/…/+page.svelte• L453-492, web/…/asset.service.ts• L86-92, web/…/asset.service.ts• L238-244

References: web/…/asset.service.ts• L86-92 web/…/asset.service.ts• L124-218 web/…/asset.service.ts• L238-244 web/…/asset.service.ts• L309-361 web/…/AssetViewerNavBar.svelte• L120-175 web/…/+page.svelte• L42-70 web/…/+page.svelte• L115-166 web/…/+page.svelte• L453-492 web/…/+page.svelte• L343-392

Search and discovery

Search results

Search converts the user’s filters into a metadata or smart-search request. Results can include assets and albums. The page loads more asset results as the user reaches the end and shows active filters as removable chips, so the query remains visible and easy to refine. web/…/+page.svelte• L66-77, web/…/+page.svelte• L123-160, web/…/+page.svelte• L258-307

The search bar separates text query modes from other filters. It can use smart context, metadata, description, full path, or OCR search when the related feature is available. Other filters cover people, dates, places, tags, media type, camera data, ratings, favorite state, archive state, and album membership. web/…/SearchFilters.svelte• L90-138, web/…/SearchFilters.svelte• L218-270, web/…/SearchTextSection.svelte• L16-39

The search manager keeps the filter state in one shape and maps it to the route query. It remembers the selected query mode in the browser. Invalid saved values fall back to smart search. Date, location, camera, tag, person, visibility, media, and rating filters are converted into the request that the search page loads. This keeps a refined search linkable and gives repeat searches a stable starting mode. web/…/search-manager.svelte.ts• L12-34, web/…/search-manager.svelte.ts• L36-98, web/…/search-manager.svelte.ts• L101-155

Search results use the same viewer and bulk actions as the main library, which makes discovery lead directly to management. web/…/+page.svelte• L315-325, web/…/+page.svelte• L343-392

References: web/…/+page.svelte• L66-77 web/…/+page.svelte• L123-160 web/…/+page.svelte• L258-325 web/…/SearchFilters.svelte• L90-138 web/…/SearchTextSection.svelte• L16-39 web/…/search-manager.svelte.ts• L36-155

Explore entry points

Explore gives the user short paths into common discovery groups rather than a full search form. It presents people, places, memories, and recent assets. A place opens a location search, a memory opens the memory viewer, and a recent asset opens the focused asset viewer. web/…/+page.svelte• L27-64, web/…/+page.svelte• L68-183

These entry points connect summary cards to the same routes used by the main library. The user can move from a group preview to a full collection without learning a second viewing model. web/…/+page.svelte• L70-152

References: web/…/+page.svelte• L27-64 web/…/+page.svelte• L68-183

Memory collections

Memories are dated asset collections shown as a separate discovery lane. The page separates upcoming memories from current memories and can filter the list by saved state or upcoming status. A settings control applies the user’s memory preferences and refreshes the collection. Birthday memories have a distinct visual cue and an age label in the viewer. web/…/+page.svelte• L25-39, web/…/+page.svelte• L42-91, web/…/MemoryCard.svelte• L16-57, web/…/MemoryViewer.svelte• L74-81, web/…/MemoryViewer.svelte• L320-353

The memory viewer treats a memory as a guided sequence. It plays photos and videos with progress, supports adjacent memories, and exposes asset actions such as favorite, download, album placement, archive, tags, and deletion. The manager can load a memory reached by a direct link, keeps adjacent memory links available, and moves away from the current URL before removing an asset or memory. web/…/memory-manager.svelte.ts• L123-180, web/…/memory-manager.svelte.ts• L200-217, web/…/memory-manager.svelte.ts• L232-300, web/…/MemoryViewer.svelte• L149-176, web/…/MemoryViewer.svelte• L278-307

References: web/…/memory-manager.svelte.ts• L72-110 web/…/memory-manager.svelte.ts• L123-180 web/…/memory-manager.svelte.ts• L200-300 web/…/+page.svelte• L25-91 web/…/MemoryViewer.svelte• L149-176 web/…/MemoryViewer.svelte• L278-307

People collections

People discovery groups assets by recognized person. The people page supports name search, URL-based filters for sharing, favorites, and hidden people, plus paged loading that restores the user’s prior scroll position. Hidden people stay out of the normal list unless the user asks to see them. web/…/+page.ts• L8-31, web/…/+page.svelte• L43-123, web/…/+page.svelte• L175-207, web/…/+page.svelte• L280-364

Each people card links to that person’s asset collection and provides a context menu for editing, hiding, merging, favoriting, or managing access. The menu changes the favorite action to match the person’s current state and sends changes through the shared person update flow. web/…/PeopleCard.svelte• L1-59, web/…/person.service.ts• L27-69, web/…/person.service.ts• L81-140

Each person page turns a people result into an asset collection. The user can inspect and manage the person, rename or merge matching people, hide the person, choose a feature photo, and correct asset assignments. The collection uses the same timeline, focused viewer, and bulk asset actions as other library views. web/…/+page.svelte• L70-115, web/…/+page.svelte• L149-221, web/…/+page.svelte• L276-357, web/…/+page.svelte• L476-548

People changes arrive through events and update the list or detail view without requiring a full return to the people page. If the current person becomes hidden, the detail route returns to its previous location. web/…/+page.svelte• L266-273, web/…/+page.svelte• L291-302

References: web/…/+page.ts• L8-31 web/…/+page.svelte• L43-123 web/…/+page.svelte• L125-207 web/…/+page.svelte• L266-364 web/…/PeopleCard.svelte• L1-59 web/…/person.service.ts• L27-69 web/…/+page.svelte• L70-115 web/…/+page.svelte• L149-221 web/…/+page.svelte• L276-357 web/…/+page.svelte• L476-548

Place collections

Places discovery groups library assets by the city stored in their location data. The places page filters out assets without a city, reports the number of matching cities, and lets the user search city names. web/…/+page.svelte• L17-28, web/…/PlacesList.svelte• L71-83

The page can show all place cards together or group them by country. Country groups sort by name and keep assets with no country at the end. Each card opens a city-filtered search, so a place preview leads directly to the full asset result set. web/…/PlacesList.svelte• L35-69, web/…/PlacesCardGroup.svelte• L22-59

Users can collapse country groups. The collapsed state follows the selected grouping mode and feeds the page controls with the current group IDs, so the controls can act on the visible groups without changing the asset query. web/…/PlacesList.svelte• L78-87, web/…/PlacesCardGroup.svelte• L18-32, web/…/places-utils.ts• L21-63

References: web/…/+page.svelte• L17-50 web/…/PlacesList.svelte• L35-87 web/…/PlacesCardGroup.svelte• L18-59 web/…/places-utils.ts• L21-63

Albums and sharing

Album organization

Albums give users a named collection that can contain selected library assets. The album list combines owned and shared albums according to the selected filter. Users can search album names and descriptions, switch between card and list views, sort the results, and group them by year or owner. web/…/AlbumsList.svelte• L117-152, web/…/+page.svelte• L21-57

The list reacts to album updates, deletes, and shared-link changes. Empty unnamed albums created during editing are removed when editing is allowed. This keeps album summaries aligned with changes made from an album page or sharing controls. web/…/AlbumsList.svelte• L159-193

An album page adds assets, removes assets, changes its name and description, selects a cover, downloads its contents, and can show a map or slideshow. Editors can change the title and description in place. The page updates those changes through album events so the list and album view stay aligned. web/…/+page.svelte• L303-314, web/…/+page.svelte• L341-447, web/…/+page.svelte• L497-562, web/…/AlbumTitle.svelte• L21-35, web/…/AlbumDescription.svelte• L18-29

Album access has roles. Owners can manage the album. Editors can add or remove content where allowed. Viewers can see shared content without receiving the same edit controls. The page reflects these roles in its sharing controls and action set. web/…/+page.svelte• L220-241, web/…/+page.svelte• L253-265, web/…/AlbumDescription.svelte• L33-49

References: web/…/AlbumsList.svelte• L117-193 web/…/+page.svelte• L21-57 web/…/+page.svelte• L220-241 web/…/+page.svelte• L253-265 web/…/+page.svelte• L303-314 web/…/AlbumTitle.svelte• L21-35 web/…/AlbumDescription.svelte• L18-49

Shared access

Sharing creates a link for an album or for selected individual assets. A shared link can control download, upload, metadata display, password protection, expiration, and its public slug. The public route uses the same asset viewing concepts but applies the link’s permissions instead of the signed-in user’s controls. web/…/album.service.ts• L56-100, web/…/+page.svelte• L18-45, web/…/+page.svelte• L1-12

The owner manages links from the shared-link area. The link settings form is the contract between private management and public use. For example, a public viewer can download only when the link permits it, while the owner can still manage the link. web/…/asset.service.ts• L135-160, web/…/+page.svelte• L49-74

References: web/…/album.service.ts• L56-100 web/…/asset.service.ts• L135-160 web/…/+page.svelte• L18-45 web/…/+page.svelte• L49-74 web/…/+page.svelte• L1-12

Downloads and export

Asset downloads

The browser downloads one asset as an original media file or downloads many selected assets as an archive. A single asset can include the motion part of a live photo when the user’s download settings allow it. Album downloads use the same archive path with the album as the source. web/…/DownloadAction.svelte• L21-32, web/…/asset.service.ts• L364-412, web/…/album.service.ts• L355-357

Download permission follows the current access context. Signed-in users can download their permitted assets. Public viewers depend on the shared link’s download setting. The browser gives progress or completion feedback through the download flow rather than treating export as an instant view change. web/…/asset.service.ts• L142-160, web/…/download-manager.svelte.ts• L3-28

References: web/…/DownloadAction.svelte• L21-47 web/…/asset.service.ts• L142-160 web/…/asset.service.ts• L364-412 web/…/album.service.ts• L355-357 web/…/download-manager.svelte.ts• L3-28

Trash and recovery

Deleted asset handling

Trash is a separate library view for assets that are no longer in the active timeline. It tells the user how long items remain before permanent deletion and supports selecting assets for restore or permanent removal. The view is available only when the trash feature is enabled. In selection mode it replaces the normal page actions with bulk restore and permanent-delete controls. web/…/+page.svelte• L27-43, web/…/+page.svelte• L46-77

Deletion from other library views removes an asset from the current view and can offer undo behavior. Restore returns the asset to the active library route, while permanent deletion stays within the trash workflow. This separation keeps normal browsing focused on active assets and makes destructive actions explicit. web/…/+page.svelte• L151-155, web/…/+page.svelte• L72-77, web/…/TimelineAssetViewer.svelte• L118-161

References: web/…/+page.svelte• L27-31 web/…/+page.svelte• L46-77 web/…/+page.svelte• L151-155 web/…/TimelineAssetViewer.svelte• L118-161

Workflow configuration

Workflow editing

The workflow page lets a user define an automated task as a trigger followed by ordered steps. It supports a visual editor for normal changes and a JSON editor for direct structured changes. A workflow can be enabled, named, described, reordered, expanded, or reduced before it is saved. web/…/+page.svelte• L54-93, web/…/+page.svelte• L95-180, web/…/+page.svelte• L305-428

The page treats editing as a draft until the user saves. It warns before navigation when unsaved changes exist, and it accepts update or delete events so another change can refresh the page or return the user to the workflow list. The surrounding actions also provide access to logs, duplication, JSON copy, download, and deletion. web/…/+page.svelte• L182-243, web/…/+page.svelte• L245-281

References: web/…/+page.svelte• L54-93 web/…/+page.svelte• L95-180 web/…/+page.svelte• L182-281 web/…/+page.svelte• L305-428

Change checklist

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

  • Keep the route’s asset scope and the Timeline options aligned. A mismatch can show the right shell with the wrong asset set.
  • Preserve the asset-grid and viewer route contract. Changes to assetId or at state can break deep links and return-to-scroll behavior.
  • Keep viewer removal, neighbor navigation, undo, and live asset updates aligned. The open asset must not remain on a route after it leaves the current scope.
  • Keep upload result handling aligned with album events. A successful upload can also require an album membership update.
  • Keep shared-link permissions aligned between link editing, public viewing, and asset download actions.
  • Keep ownership, album-role, and keyboard-shortcut checks consistent between single-asset actions and bulk selection actions.
  • Keep the search manager’s filter mapping aligned with the search controls and route query. A new filter can appear in the UI without reaching the search request.
  • Keep people filters in the URL and keep saved scroll pages compatible with the current paging behavior.
  • Keep person card menus and person-page actions aligned with the person service. State-based actions such as favorite and hide must update the same people views.
  • Keep person hide, merge, rename, feature-photo, and asset-assignment events aligned between the people list and person detail route.
  • Keep memory preference changes applied to the memory manager before the page renders its new groups.
  • Keep the memory URL position valid when removing a memory or its last asset. The viewer must leave a deleted position before the data is removed.
  • Keep place search and country grouping aligned with the assets that have city data. A change to the place scope must also preserve group IDs used by the controls.
  • Keep place group collapse state keyed by the active grouping mode. Switching between ungrouped and country views must not apply stale collapse state.
  • Keep album title, description, cover, and membership changes aligned with album update events. A saved field or asset change must update the current album and other album views.
  • Keep album-list filters, search, grouping, and sorting based on the same owned and shared album sets. A new album event must update both sets.
  • Keep duplicate and upload error states visible in the upload panel. Silent queue failures leave the user without a reliable intake result.
  • Keep activity initialization and comment permissions aligned with the shared album state. A panel can show album-wide reactions even when no asset is selected.
  • Keep stack and live-photo selection rules aligned with the timeline updates. Linking or unlinking must remove and restore the correct assets in the current view.
  • Keep album selection modes separate from normal route navigation. Adding assets or choosing a cover must not lose the user’s prior grid position.
  • Keep visual and JSON workflow edits mapped to the same saved workflow shape. Unsaved drafts must remain protected by the navigation prompt.

Important failure modes

TriggerConsequenceGuard
A route changes asset scope without changing its timeline optionsThe grid can show assets from the wrong view or fail to restore the selected assetDefine the scope in the route and pass matching options to Timeline
The viewer loses the assetId or grid at stateBack navigation can return to the wrong position or fail to open a direct asset linkPreserve route updates and the timeline’s scroll restoration contract
The current viewer asset leaves the timeline without neighbor or close navigationThe browser can remain on an asset that no longer belongs to the current viewUpdate the timeline before the action and move to the next asset, previous asset, or grid
An upload is accepted but the album-add step is skippedThe file reaches the library but does not appear in the album the user choseTreat upload and album membership as one user workflow
A search control updates local state but not the route queryThe page can show a filter that the server does not applyKeep SearchManager conversion and filter controls in step
A people filter or name search is kept only in local stateReloading or sharing the URL loses the intended people scopeTreat the URL query as the source for people filters and search
A memory preference change does not reapply the memory manager queryThe settings indicator changes but the memory list stays staleApply saved settings through the memory manager before showing the result
A memory asset is deleted before the viewer leaves its URLThe browser can remain on a position that no longer existsNavigate to an adjacent memory or the memory list before removal
A place search uses assets without city data or ignores the normalized queryThe result count and cards can disagree with the search fieldFilter the place scope first and use the same normalized city query for cards and count
Place group IDs are not refreshed after filtering or regroupingGroup controls can collapse or expand the wrong country sectionsDerive group IDs from the current grouped result set
Public download rules differ from shared-link settingsA link can expose a download action that should be blocked, or block one that should be allowedUse the shared link permission when building public asset actions
An album edit or membership change succeeds without an album update eventThe album page or list can keep stale content or title textEmit and handle the album update after saving or changing album data
Album list state uses only owned albums after a shared album updateA shared album can disappear until the page reloadsApply album update and delete events to both owned and shared collections
A deleted asset is removed from the view without an undo updateThe UI stays stale after the user restores the assetUpdate or reload the active timeline after delete and restore events
Bulk controls or their shortcuts ignore ownership or album roleA user can see actions that the current access context cannot completeDerive visible and keyboard actions from the same ownership and role rules as single-asset actions
Activity is loaded for the wrong album or remains open after activity is disabledThe panel can show stale reactions or allow comments that the album does not permitInitialize and reset activity with the album route and activity state
A live-photo link updates only one side of the pairThe timeline can show a duplicate motion asset or lose the still asset after unlinkingUpdate the timeline for both assets after link and unlink actions
Workflow visual and JSON drafts use different saved fieldsA user can save one editor’s view while silently losing changes from the otherConvert both editors to the same workflow content before save
Navigation ignores unsaved workflow changesA draft can disappear when the user changes route or closes the pageKeep the navigation guard active until the save or explicit confirmation completes

Key files

FileWhy to read it
web/…/Timeline.svelteShows the common asset grid, route-aware scrolling, selection behavior, and viewer handoff.
web/…/TimelineAssetViewer.svelteShows how the focused viewer follows timeline order and reacts to asset removal, undo, upload, and update events.
web/…/+page.svelteShows the main personal library, memory entry cards, empty-library upload entry, live-photo linking, stack actions, and bulk asset actions.
web/…/AssetViewer.svelteShows the focused viewing, navigation, media, metadata, edit, and activity experience.
web/…/AssetViewerNavBar.svelteShows how viewer actions change with ownership, asset state, album context, and public sharing.
web/…/PhotoViewer.svelteShows focused photo controls and visual data overlays.
web/…/ActivityViewer.svelteShows shared album comments, likes, time grouping, and reaction access.
web/…/file-uploader.tsShows the browser upload contract, duplicate result, album follow-up, and error state.
web/…/UploadPanel.svelteShows how users see and control upload progress.
web/…/+page.svelteShows filtered and smart search results with paging and shared asset actions.
web/…/search-manager.svelte.tsShows how search controls become linkable route queries and how query modes persist.
web/…/+page.svelteShows the discovery shortcuts for people, places, memories, and recent assets.
web/…/+page.svelteShows memory grouping, preference entry, saved-state display, and links into guided memory viewing.
web/…/memory-manager.svelte.tsShows memory paging, saved-state filtering, direct-link loading, adjacent navigation, and removal behavior.
web/…/MemoryViewer.svelteShows memory playback, asset navigation, memory actions, and return to the main timeline.
web/…/+page.tsShows how people search and filter state becomes the initial people collection.
web/…/+page.svelteShows people search, filters, paging, scroll restore, naming, merging, and access controls.
web/…/PeopleCard.svelteShows the people collection card, person route entry, and contextual person actions.
web/…/+page.svelteShows the person asset collection, person management, assignment correction, and shared timeline actions.
web/…/+page.svelteShows the places route, city search, visible result count, and place view settings.
web/…/PlacesList.svelteShows place filtering, country grouping, result state, and group IDs for controls.
web/…/PlacesCardGroup.svelteShows place cards, city-search links, and collapsible country groups.
web/…/places-utils.tsShows how place group collapse state follows the active grouping mode.
web/…/+page.svelteShows the album list entry point and its owned/shared album views.
web/…/AlbumsList.svelteShows album filtering, search, grouping, sorting, view choice, and event-driven list updates.
web/…/+page.svelteShows album content, role-aware controls, upload and asset selection, cover selection, activity, sharing, and download entry points.
web/…/album.service.tsShows the browser actions that connect uploads, album membership, sharing, and album export.
web/…/asset.service.tsShows asset actions, permission-aware downloads, album removal, and keyboard shortcuts for asset management.
web/…/+page.svelteShows the settings that define public link behavior.
web/…/+page.svelteShows the separate restore and permanent-delete workflow.
web/…/+page.svelteShows workflow triggers, ordered steps, visual and JSON editing, save protection, and route actions.