Skip to content

v4.5.0

Choose a tag to compare

@jaimetur jaimetur released this 20 Jul 18:27
· 252 commits to main since this release

🗓️ CHANGELOG

Planned Roadmap for the following releases
Changelog for the past releases


Release: v4.5.0

Release Date: 2026-07-18

🚨 Breaking Changes:

  • Removed the discontinued Immich Photos -> Remove Orphan Assets module from all exposed interfaces (Web, CLI, TUI, and GUI) and from the related Immich documentation, while keeping the underlying implementation paths commented/preserved in code for possible future reuse.

🌟 New Features:

  • Added a new cloud-only Consolidate Albums Names feature for Google Photos, Synology Photos, Immich Photos, and NextCloud Photos, available from CLI, Web Interface, TUI, and desktop GUI. This action reuses the same equivalent-album-family detection logic as --consolidate-similar-albums but operates entirely in the destination cloud without uploading new assets. On targets that support album deletion (Immich, Synology, NextCloud), redundant albums are removed after confirmed reassignment; on Google Photos, redundant variants are kept because the public API cannot delete albums.
  • Added an Estimated Time indicator to the Automatic Migration live dashboard in both the terminal UI and the Web Interface. The estimate is computed from the current elapsed time, the number of already pulled assets, and the remaining pending assets (total_assets - pulled_assets), so long-running migrations now show an approximate remaining duration without being skewed by duplicate-heavy push phases.
  • Added the optional --one-time-password flag to Automatic Migration across the Web Interface, CLI TUI, and desktop GUI whenever either the selected source or target is Synology, so Synology 2FA migrations can be configured directly from those UIs instead of only from the Synology-specific cloud module. (Issue #1174).
  • Split the Docker Web Interface main workspace into two dedicated pages, Features and Configuration, while keeping the shared hero/header and authentication flow. The root web route now redirects to the Features workspace, and users can switch between both pages from a dedicated top-level tab navigation.
  • Added a dedicated top-level Web Interface tab-strip for Features and Configuration, visually separated from the documentation buttons and styled as a workspace selector instead of a generic button row. This makes the active working context much clearer when moving between execution and configuration tasks.
  • Added a new descriptive card above Configuration Panel -> General Arguments, explaining the purpose of shared/global arguments and listing them grouped by the same categories used in the editor cards (Logs, Execution, Naming & Folders, Filters, and Other).
  • Added new descriptive cards above Configuration Panel -> Features Config and Configuration Panel -> App Settings, so all three configuration sub-tabs now include an inline help summary consistent with the documentation cards already used by Takeout and cloud feature panels.
  • Replaced the previous top-level Features / Configuration navigation buttons in the Web Interface with integrated tab-style selectors attached to their corresponding panels, so workspace switching now follows the same visual language as the internal feature/configuration tab systems.
  • Added a dedicated Process Input panel to the Web Interface Output Panel, placed below the live log and above the Run / Stop buttons. When a running job requests interactive input, the web UI can now send free-form text directly to the process stdin, while still preserving the existing quick Yes / No shortcuts.
  • Promoted the Web Interface Output Panel into its own top-level workspace tab and page, placed between Features and Configuration, so execution output can now be opened independently while preserving the same natural tab navigation style as the other main workspaces.

🚀 Enhancements:

  • Added targeted DEBUG performance traces for Automatic Migration local-folder pipelines and the Web Interface live log/dashboard path. Debug logs now include per-asset pull/push/album-association timing plus backend dashboard snapshot/output processing timings, and the browser can emit optional console.debug render timings when debug_web_perf=1 or localStorage.photomigrator_web_perf_debug = \"1\" is enabled.
  • Reworked the Web Interface Automatic Migration live dashboard so its counters no longer depend on reparsing the execution log. The migration subprocess now emits structured dashboard snapshots, the backend persists them per job, and every browser session receives the same synchronized counters after refresh or from another device without needing the full log history.
  • Refined the Web Interface operator flow around module execution. The Execution Output panel now includes its own Run module / Stop module button pair in addition to the existing controls in Feature Selector, and the Feature Selector title now shows the currently selected module name (for example Feature Selector: Automatic Migration or Feature Selector: Immich Photos) so the active working context stays visible while scrolling elsewhere in the page.
  • Refined Automatic Migration DEBUG performance logs so the real destination upload time is now emitted separately as automatic_migration.asset.upload, while the end-to-end asset lifecycle is reported as automatic_migration.asset.pipeline. This makes it much easier to distinguish backend upload cost from queue wait, album-association batching, and post-upload cleanup/finalization delays.
  • Restricted live cProfile dumps during Automatic Migration to VERBOSE mode only, and preserved the effective runtime log level inside the migration pipeline so DEBUG diagnostics such as [PERF] pull/push traces remain visible when --log-level debug is used.
  • Refined reusable/similar album consolidation so semantic split suffixes such as Día 1, Day 2, Jour 3, Parte 4, Part 5, Session 6, and their common variants in major languages (with or without spaces, dashes, or underscores before the suffix) are normalized back to the shared base album name during similar-album grouping, while post-reassignment confirmation now refreshes keeper-album membership each time before deciding whether a redundant album can be removed.
  • Reworked Consolidate Albums Names family discovery into a shared cloud utility used by Google Photos, Synology Photos, Immich Photos, and NextCloud Photos. The scan now groups albums by reusable-name family in a single pass instead of rebuilding the full family plan for every album, which reduces duplicate work on large libraries and keeps the preview/keeper-selection logic consistent across all cloud targets.
  • Hardened Automatic Migration album-association confirmation for targets such as Immich and Synology. After associating a batch, PhotoMigrator now re-reads the destination album membership and, when needed, performs a short delayed second refresh before warning and scheduling a delayed retry, avoiding false negatives when the target actually associated the asset but exposes the new membership with a small delay.
  • Reworked Automatic Migration album association into a hybrid flow. When the destination upload immediately returns a reusable target asset id, PhotoMigrator now associates that asset to its destination album right away inside the push worker so an interrupted migration still leaves most already-uploaded assets attached to their album. Only the expensive duplicate-id resolution path and the assets that still do not have a reusable destination id are deferred for later recovery/finalization.
  • Deferred only the unresolved portion of Automatic Migration album association until the source album has finished pulling by default. Album-bound uploads that already have a reusable destination id are associated immediately during the hot push path, while duplicate-heavy or unresolved assets are accumulated and resolved once the puller marks that source album as complete. This keeps interruption safety for already-uploaded assets while still removing the expensive duplicate-id lookup work from the main hot path.
  • Disabled automatic Automatic Migration push retries and album-association verification retries by default. Failed uploads are now treated as single-attempt failures unless the user explicitly re-enables retries, which keeps the hot path free of delayed re-enqueues and leaves failed files in the Automatic_Migration_Push_Failed_* temp folder for manual inspection or a later rerun.
  • Added automatic multi-worker album association with per-destination-album locking for the new Automatic Migration album-association stage, together with target-specific auto-tuned batching/flush behavior.
  • Split Automatic Migration retries into two separate behaviors: real upload failures still use the normal delayed push-retry pipeline, while unconfirmed album associations now use short verification retries without being counted as upload retry attempts. This avoids misleading attempt 1/3 push retries for duplicate-resolved assets whose upload already succeeded but whose album membership was not yet confirmed by the target.
  • Hardened Automatic Migration album association recovery for Immich targets when POST /api/albums/{id}/assets returns ambiguous 400/500 responses. Before warning that album membership was not confirmed, PhotoMigrator now refreshes the destination album membership, retries unresolved assets individually, and performs one last membership refresh so assets that were actually associated by Immich are confirmed instead of being left as false-negative warnings or unnecessary follow-up retries.
  • Reduced the default Immich album-association batch size and now use API-confirmed per-asset add-to-album results before forcing a full destination album re-list, which lowers queue stalls and avoids unnecessary full membership refreshes on large duplicate-heavy migrations.
  • Prioritized Automatic Migration push scheduling so photo/live-photo uploads are drained ahead of regular video uploads by default. This does not change the raw network/server upload speed, but it reduces artificial queue buildup from long-running video uploads monopolizing push workers while faster photo uploads are waiting.
  • Added explicit Album Finalize Waiting progress diagnostics during Automatic Migration whenever an album cannot yet be counted as Album Pushed because it is still active, still has pending local files, or is waiting on duplicate-resolution/association cleanup. This makes stalled album progress visible in logs instead of failing silently while the album is still legitimately incomplete.
  • Reduced the default Automatic Migration album-association verification retry delays from 2s/10s/30s to 2s/5s/10s. These retries are only used to re-check delayed album membership confirmation after a successful upload or duplicate resolution, while real push-failure retries still keep their longer independent delay policy.
  • Reworked cloud Automatic Migration album handling across Immich, Synology, Google Photos, and the other cloud targets so the hot upload path now creates/reuses the exact working album first, immediately associates assets whose upload already returned a reusable destination asset id, and defers only the expensive duplicate-id resolution plus final canonical/similar-album consolidation to album-finalization time. Duplicate uploads rejected without a returned destination id are now kept in a per-album pending-resolution list and are resolved only once the source album finishes, which removes per-asset remote duplicate lookups from the main upload path while preserving correct album membership before the temporary album folder is cleaned up.
  • Extended the Automatic Migration final summary with album-reuse stats (Consolidated Albums, Canonicalized Albums) and now auto-runs target remove_empty_albums() at the end when the destination client supports it.
  • Reduced the Web Interface Execution Output refresh interval to 250 ms, so live job output appears closer to real time while preserving the current structured-dashboard and compact-log pipeline.
  • Formalized and expanded the shared photo-client public contract used by cross-backend features such as Automatic Migration and the other cloud/local modules. A new base client contract now defines the common polymorphic operations and broader shared API surface, including album creation/listing, album asset listing, add-to-album, push/pull operations, upload/download workflows, album-maintenance actions, and common helpers such as album_exists, get_album_assets_count, get_album_assets_size, and get_assets_by_filters. The concrete Local Folder, Synology Photos, Immich Photos, NextCloud Photos, and Google Photos clients were updated to expose homogeneous public method names and argument names across operations such as push_albums, push_no_albums, push_all, pull_albums, pull_no_albums, pull_all, remove_all_albums, remove_empty_albums, remove_duplicates_albums, merge_duplicates_albums, and remove_all_assets. Optional context parameters that only matter for specific backends (for example Synology album context) are now accepted consistently as no-ops by the other clients where applicable, and the contract-signature test was extended to catch future interface drift automatically before it becomes a runtime failure.
  • Extended Automatic Migration album-completion logging so each Album Pushed line now includes a per-album asset summary with Total Assets, Pushed, and Duplicates, plus Failed when applicable. These counters are accumulated from the real migration events per source album, so long-running runs now expose the final per-album outcome directly in the log without having to infer it from scattered asset-level lines.
  • Optimized the Web Interface live polling path for very low refresh intervals. Job polling now runs as a chained single in-flight loop instead of setInterval, so the browser never overlaps multiple /api/jobs/{id} requests when a previous poll is still being processed. The polling endpoint also supports a compact response path and now exposes an output_version counter, allowing the frontend to skip log repaints and dashboard refreshes when neither the compact log buffer nor the structured dashboard snapshot changed. This reduces unnecessary backend recomposition, JSON serialization, and frontend render work during progress-heavy runs and avoids the severe execution slowdown previously observed when aggressively lowering the poll interval to 25-50 ms.
  • Simplified the Web Interface live log pipeline to the minimum processing model. The backend now keeps only complete visible log lines plus in-place progress-line replacement on \\r, strips embedded __PHOTOMIGRATOR_DASHBOARD__ snapshots from the visible stream, and avoids the previous extra log repairs such as orphan level-prefix reconstruction, GPTH-specific prefix stitching, embedded progress/log line splitting, and paginated log-history APIs. The frontend now just polls the compact output_lines, colors each complete line by type, preserves manual selection freeze, and applies the existing auto-scroll / near-bottom behavior without virtualized history windows or additional client-side progress reinterpretation.
  • Added a cheap fast-path to the Web Interface live log parser so the expensive GPTH/progress repair heuristics now run only for lines that actually look like progress bars or progress-followup records. Regular log lines now bypass the progress-specific splitting, prefix inheritance, and progress-key reconstruction logic, reducing backend overhead during high-frequency Automatic Migration polling while preserving the corrected GPTH bar rendering.
  • Enhanced the Web Interface live log progress detection so indeterminate tqdm-style counters such as Organizing files with year/month structure ... 128557 files [02:01, 1346.55 files/s] are now recognized as progress updates and compacted in place instead of flooding the visible log with one line per refresh during long post-processing phases.
  • Refined the Automatic Migration live dashboard Estimated Time calculation so it now starts from the real beginning of the asset transfer phase (pull/push workers launch) instead of the earlier module/job start. This prevents long Google Takeout or other preprocessing stages from inflating the ETA by hours before the first assets actually begin to move.
  • Extended the defensive Google Takeout post-GPTH special-folder reclassification to normal GPTH --input/--output runs as well. PhotoMigrator now also scans the final processed output of standard GPTH executions and moves localized Archive / Trash / Locked Folder variants such as Carpeta privada out of Albums into Special Folders before publishing the processed library.
  • Added a lightweight hot cleanup pass for Automatic Migration --move-assets true local sources so once an album is truly finalized as Album Pushed, PhotoMigrator now also tries to remove the corresponding emptied source album folder immediately instead of waiting only for the final cleanup pass. The final local-source cleanup was also hardened to treat runtime housekeeping markers such as .active and *.lock as ignorable emptiness artifacts together with the existing excluded Synology/system files.
  • Reworked the Web Interface live log transport and renderer to use incremental output operations instead of full log snapshots on every poll. The backend now keeps a lightweight append/replace operation stream for completed visible lines, while the frontend applies only the delta to persistent DOM nodes and groups historical lines into content-visibility blocks. This preserves the current progress-bar rendering, copy/selection behavior, and immediate scrolling across all already painted lines, but avoids the previous O(total visible log) HTML rebuild on each refresh as long-running jobs grow their output.
  • Refined Automatic Migration live dashboards across the Web Interface and terminal dashboard so queue/backlog metrics are now split into three explicit bars: Assets in Queue (real push queue only), Album Assoc Queue, and Delayed Retries. The dashboard also now shows Blocked Assets immediately below Blocked Albums, renames Invalid Files to Unknown Files, moves the elapsed/remaining timers into the Pull panel with a visual separator, adds Delayed Recovered / Delayed Failed counters to the Push panel, and counts real iCloud metadata CSV inputs as Total Metadata while excluding generic generated reports such as Photo Details.csv mismatches, Unresolved_Assets.csv, or No_Date_Assets.csv.
  • Reworked Automatic Migration physical asset accounting and post-upload cleanup semantics. Pull/push/duplicate/failure counters now stay aligned to the real physical files represented by each staged upload bundle, including Immich live-photo pairs where one queued photo item also carries a companion video. In addition, assets whose upload succeeded but whose destination album association still could not be confirmed are no longer deleted from the temp staging area: PhotoMigrator now removes them from the source when --move-assets true is enabled, preserves the staged files under Automatic_Migration_Push_Failed_*/Album Association Failed/<AlbumName>/, and keeps Album Assoc Unconfirmed as an informational follow-up counter instead of folding it into the hard Push Failed Assets total.
  • Extended the shared valid-photo extension handling so .webp files (for example IMG_20210805_112248_719.webp) are now treated as supported photo/image assets consistently across the local-folder and Synology-backed workflows instead of being classified as unknown/unsupported files.
  • Refined the Web Interface tab theming so the main workspace tabs (Features, Output, Configuration) and the secondary Configuration tabs now use stronger theme-aware color palettes, making the active workspace and configuration context more visually prominent while preserving the attached natural-tab layout.
  • Refined the Web Interface execution controls so the Features and Output workspaces now use compact, uniform-width Run / Stop action buttons, dangerous-run confirmations use the same shorter wording, and starting a job from Features now switches automatically to the Output workspace as soon as execution begins.
  • Improved Immich Photos long-running module feedback so operations that spend noticeable time listing albums, gathering album assets, collecting assets without albums, or scanning local upload trees now emit an explicit progress message before the first tqdm bar appears. This removes the silent waiting period previously seen in modules such as Remove Empty Albums, Remove Duplicate Albums, Remove All Albums, Pull Albums, Pull All, and the upload flows, without adding extra parsing load to the Web Interface log pipeline.
  • Refined the Web Interface Command Preview so it now displays a compact PhotoMigrator ... command instead of the full Python interpreter and .py launcher path, and aligned the real execution order with that same preview ordering. Context-defining arguments such as --client, --account-id, --source, --target, and the main action flag are now shown and executed first, while secondary album-normalization flags such as --consolidate-similar-albums and --prefer-canonical-album-names are pushed near the end just before --configuration-file.
  • Refined the Web Interface cloud User Description cards so the Supported modules list is now displayed as a cleaner two-column layout without inline | separators, making the available cloud actions easier to scan at a glance.
  • Updated the Web Interface Output Panel header so it now reflects the currently selected feature and, when applicable, the selected module as well (for example: Output Panel: Immich Photos - Upload All).
  • Web Interface: while a job is running, the Output Panel now stays bound to the feature/module that is actually executing instead of following later selections made in the Features tab. This also keeps the Output Panel title aligned with the active job context until the execution finishes.
  • Reworked Automatic Migration staging into Automatic_Migration_<TIMESTAMP>/Push_Queue/. Local-folder sources now preserve their original relative directory hierarchy while assets are copied there, or moved there immediately when --move-assets=true, instead of using the old Automatic_Migration_Push_Failed_* working folder.
  • Added persistent Automatic Migration queue folders: failed uploads move from Push_Queue/ to Push_Delayed_Queue/, are retried three times at five-minute intervals, and move to Push_Failed/ after the final unsuccessful retry. Push workers now prioritize timer-ready delayed retries ahead of new Push_Queue/ work. Duplicate uploads without a reusable destination asset ID are stored in Album_Association_Queue/ and processed by dedicated album-association workers.
  • Fixed Album Assoc Queue dashboard depth to report the physical files retained in Album_Association_Queue/, including assets already held by an album-association worker for batching, instead of showing only the in-memory queue entries waiting to be claimed.
  • Moved duplicate uploads that require remote target-id resolution into Album_Association_Queue/ as well. The dedicated album-association workers now resolve the existing destination asset first and then associate it to the album, so no album-bound duplicate work remains hidden in a separate in-memory pending set.
  • Restored immediate album association for uploads and duplicates that already have a reusable destination asset id. Album_Association_Queue/ is reserved exclusively for duplicate assets that first require remote target-id resolution.
  • Updated all Automatic Migration live dashboards (Web, CLI, TUI, and GUI) so Delayed Retries Queue and Album Assoc Queue use the total number of migration assets as their progress maximum. Album Assoc Queue now appears directly below Delayed Retries Queue.
  • Grouped each Push dashboard outcome summary directly below its corresponding Assets, Photos, Videos, or Albums progress bar as Total <type> (New / Duplicates / Failed), widened Info Panel labels to keep queue names on one line, and renamed the backlog indicator to Delayed Retries Queue.
  • Changed the Delayed Retries Queue and Album Assoc Queue progress maxima to the physical assets admitted to each queue during the migration, rather than the full migration asset count. Repeated retries of the same asset do not inflate either maximum.
  • Reworked Automatic Migration Push dashboards across Web, CLI, TUI, and GUI. The Pushed Assets, Pushed Photos, and Pushed Videos bars now track physical assets once a pusher worker has removed them from Push_Queue, while New, Duplicates, and final Failed outcomes are displayed separately for each media type. Added cumulative Delayed Retries and Delayed Recovered counters; album-association follow-up failures remain excluded from hard push failures.
  • Updated Automatic Migration Pull dashboards across Web, CLI, TUI, and GUI so each indented Failed Assets, Failed Photos, Failed Videos, and Failed Albums counter is displayed directly below its matching progress bar.
  • Added an indented 🔢 counter marker to each New / Duplicates / Failed Push outcome summary across Web, CLI, TUI, and GUI.
  • Moved the Rich terminal Automatic Migration Live Dashboard renderer out of AutomaticMigration.py into LiveDashboard.py, keeping the migration orchestration and web-dashboard snapshots isolated from terminal presentation code.
  • Expanded the startup log for every feature with the selected feature and its required flags before Global Settings, followed by Optional Flags Used and Optional Flags Default sections. The latter reports effective defaults for optional flags applicable to the selected feature that were not supplied by the caller. Modular cloud and Other Features runs now also identify their selected module. Configurable flag values were removed from Global Settings, leaving only hardcoded or runtime-derived settings there.
  • Reduced the Rich Automatic Migration Live Dashboard Info, Pull, and Push panel band by one terminal row, giving the live log panel more vertical space.
  • Improved the Web Interface mobile layout for Google Takeout and iCloud Takeout by resetting their desktop card placement to a single column, and made cloud Supported modules lists render in one column on narrow screens.
  • Automatic Migration now prunes empty relative-path folders immediately after assets move between persistent staging queues or are deleted after successful processing, while retaining the queue roots themselves.
  • Corrected the initial Delayed Retries Queue and Album Assoc Queue dashboard totals so they display 0/0 before any asset enters either queue instead of showing a synthetic total of 1.
  • Reworked Local Folder symlink staging for Automatic Migration: album symlinks now materialize their target content under the album-relative queue path. With --move-assets, PhotoMigrator copies that content, removes only the original symlink, and never moves its shared physical target away from other album links.
  • Fixed Album Association Queue worker coordination: album-complete markers are now shared across all association workers, so assets claimed by a different worker no longer remain pending until the end of the migration. Immich HTTP-level album-association failures now skip wasteful immediate per-asset verification calls, retry as a batch, and log the response status/body for diagnosis.
  • Added Estimated End to every Automatic Migration live dashboard: it appears after Remaining Time in the Web dashboard header and beneath it in the Pull panel across Rich CLI, TUI, and GUI dashboards.
  • Fixed Automatic Migration album progress accounting: direct Album Association Queue admissions now increment their physical-file total, and albums whose assets finish as New, Duplicate, or final Failed are reconciled into Pushed Albums once the pipeline drains.
  • Corrected Album Association Queue outcome accounting: Album Assoc Retry Scheduled now counts the physical files admitted to Album_Association_Queue/ once rather than every retry attempt, and Album Assoc Retry Recovered only counts files whose association is actually confirmed after a retry.
  • Made Automatic Migration Pull and Push dashboard maxima consistently physical-file based. Live Photo companions now expand the effective media total instead of overflowing progress bars; Push uses successfully pulled physical files as its maximum, excluding Pull failures.
  • Standardized Automatic Migration file counters on physical files across retry, recovery, final retry failure, album-association recovery, and album-association unconfirmed outcomes. A Live Photo photo/video pair now contributes two files consistently to every applicable asset counter and queue metric.
  • Fixed Automatic Migration Album Association Queue recovery: destination-album lookup or creation failures are no longer cached as empty IDs and now retry with an explicit reason. Duplicates reported by Immich without an immediate remote ID are counted immediately as duplicates and retried in Album_Association_Queue/ instead of being moved to Push_Failed/; unresolved terminal cases are reported as album-association failures. Remote duplicate lookup now indexes the destination library by filename to avoid repeatedly scanning every asset.
  • Added Automatic Migration Pull failure auditing under Pull_Failed/: every failed pull is written to pull_failed_assets.csv with its filename, album, source/staging paths, preserved-file path, and reason. Any partial staged file is copied there with its relative hierarchy. The terminal cleanup now also removes orphaned files left in Push_Queue/ only after every push worker has stopped.
  • Raised the Automatic Migration delayed-retry eligibility limit from 50 MB to 200 MB, so files up to 200 MB can enter Push_Delayed_Queue/ and use the configured retry policy instead of moving directly to Push_Failed/.
  • Reduced Automatic Migration end-of-run log noise by suppressing only the final reconciliation Album Pushed lines. Albums now re-evaluate their normal finalization as soon as pulling completes, so their regular Album Pushed summary is emitted during the migration instead of being deferred to the final reconciliation. When album consolidation or canonical naming is enabled, each completed consolidation/canonicalization also logs its source and destination names together with the original and final destination asset counts.
  • Fixed Automatic Migration album-finalization and Album Assoc Queue reporting for local folders: albums whose drained staging directory was already pruned can now emit their normal Album Pushed summary during the migration, and queue depth ignores Synology @eaDir / __MACOSX artifacts. Immich album-association retries now invalidate and re-resolve a destination ID that returns Album not found, with an explicit protected-folder diagnostic for names such as Carpeta privada.
  • Clarified Immich Automatic Migration album-association warnings and terminal failures: they now identify assets in Immich Locked Folder without an unlocked API session as a common possible cause when association cannot be confirmed.
  • Refined Automatic Migration album association failure handling: Album_Association_Queue/ now receives only duplicate assets whose push did not return a reusable destination ID. Its workers perform the initial remote-ID lookup plus one retry by default; failures with an already known target ID remain in the hot path and move directly to Album_Association_Failed/. Repeated retry diagnostics are reduced to DEBUG, and terminal queue assets preserve their relative hierarchy in Album_Association_Failed/.
  • Corrected the Album Assoc Queue dashboard total to count only physical files actually admitted to Album_Association_Queue/; known-ID hot-path association failures are no longer represented as queued assets.
  • Renamed the Automatic Migration physical delayed upload-retry folder from Delayed_Queue/ to Push_Delayed_Queue/.
  • Added an 🚩 Album Assoc Failed terminal-outcome row to the Push panel in the Web and Rich Automatic Migration live dashboards.

🐛 Bug fixes:

  • Fixed the cloud Automatic Migration regression introduced after v4.0.0 where duplicate-heavy album uploads could become dramatically slower because the migration pipeline tried to resolve reusable destination asset ids and apply album-family consolidation in the hot path for every asset. Known-id assets are now still associated during the normal migration flow, while duplicate uploads without an immediate reusable id are postponed to a final per-album resolution pass instead of forcing repeated remote lookups during each upload.
  • Fixed the Synology Photos shared-album/shared-space follow-up regression originally surfaced from issue #1159 and later tracked as issue #1173. Shared album requests are now scoped by the current album_id instead of listing against only the shared passphrase context, which prevents runs from reusing the same unrelated asset across many albums and restores proper asset discovery for shared-space album migrations. Also stopped treating --filter-by-type all as an active filter, so Automatic Migration analysis no longer accidentally falls back into personal-space-only Synology filtering when the user explicitly wants all asset types. In addition, Synology album classification now distinguishes albums merely shared by their owner from true shared with me albums, so owner-shared albums keep using the normal owned-album asset listing flow and are no longer incorrectly blocked just because their invitees have view permissions.
  • Fixed an Automatic Migration regression introduced by the new Synology blocked-shared-album guard. Non-Synology sources such as Local Folder and processed Google Takeout no longer call Synology-only helpers during album analysis/pull, so local migrations no longer abort with AttributeError: 'ClassLocalFolder' object has no attribute 'is_blocked_shared_album'.
  • Fixed an Automatic Migration race in the local/Takeout staging pipeline where a duplicate-detected asset could delete a staged file or live-photo companion that had already been dequeued by another push worker but was still being uploaded. Staged files are now treated as reserved both while queued and while actively in-flight, preventing File not found: .../Album/<name>.MP4 failures caused by premature cleanup during duplicate handling.
  • Fixed another Automatic Migration local/Takeout live-photo staging bug for Immich targets. When a photo was enqueued together with a same-stem video companion for push_live_photo(), that companion path could still be discovered later as a standalone video asset, copied back into the temp album folder, and only fail much later with File not found or leave orphan .MP4 files after the photo workflow had already consumed and cleaned it. Live-photo companion paths are now reserved as consumed as soon as the paired photo is queued, so they are no longer re-enqueued later as independent video uploads.
  • Fixed an additional Automatic Migration Immich live-photo staging edge case where a same-stem companion video could already be sitting in the push queue as a standalone asset before the paired photo later claimed it for push_live_photo(). Those consumed companion paths are now explicitly marked and skipped both while enqueuing and again inside the push worker, so they no longer survive long enough to fail later with File not found: .../<name>.MP4 after the paired photo workflow has already consumed and cleaned them.
  • Fixed Synology Photos album-context handling for Shared Space, true shared with me albums, and regular owned albums. PhotoMigrator now documents and follows the browser-observed Synology API behavior more closely: albums surfaced under normal_share_with_me are no longer blindly treated as passphrase-based shared albums, Shared Space albums owned by the current user prefer the browser-style SYNO.Foto.Browse.Item version=7 listing flow with album_id, and album downloads now also include album_id context with passphrase fallback only for true shared-with-me cases. This resolves the remaining #1173 gap where Shared Space albums were detected but their assets could not be listed/downloaded correctly. (Issue #1173).
  • Fixed Synology Photos owner-id learning for Shared Space albums so normal_share_with_me albums can still be reclassified as owned even when no personal albums were seen first. (Issue #1173).
  • Fixed Synology album asset listing fallbacks so Automatic Migration and Download Albums keep trying alternate item-list variants when album counts are missing instead of treating the first empty success response as a truly empty album. (Issue #1173).
  • Fixed the Web Interface log stream so inline __PHOTOMIGRATOR_DASHBOARD__ snapshots no longer leak into progress lines, create blank lines, or leave stray INFO : fragments in Execution Output.
  • Fixed the Web Interface Execution Output panel so manual text selection is preserved while Auto Scroll is disabled even if a live progress bar keeps updating, and added Ctrl+C / Cmd+C copying for the currently selected log text.
  • Fixed local-source cleanup so folders containing only excluded Synology artifacts such as @eaDir, @Recycle, .DS_Store, or thumbnail files are now treated as empty and can be removed both during album completion and in the final cleanup pass.
  • Fixed another Synology Photos / Automatic Migration follow-up around issue #1173. --filter-by-type all is now treated consistently as “no active filter” inside the migration pipeline as well, so Synology Shared Space runs no longer fall into the filtered album-validation path during analysis or pulling. In addition, Synology shared-album classification now also reads owner/permission details when sharing_info is returned at the top level of the album payload instead of only under additional, which improves reclassification of normal_share_with_me albums that are actually owned by the current user and keeps them on the correct Shared Space listing/download flow. (Issue #1173).
  • Fixed the Web Interface Execution Output auto-scroll behavior so scrolling upward now disables live tail following automatically, and returning near the latest visible lines re-enables Auto Scroll automatically without requiring a manual toggle.
  • Fixed the Web Interface module-launch flow so starting any new execution now re-enables Auto Scroll automatically before the fresh job output begins, preventing a previous manual scroll-up state from leaving the new run stuck without live tail following.
  • Fixed an Automatic Migration client-interface regression where Synology-specific album context arguments such as album_scope, album_expected_count, and album_id could leak into generic source-client calls during album pulling, breaking non-Synology sources like Local Folder with unexpected keyword argument errors. The migration pipeline now only sends those extra kwargs when the active source client is actually Synology Photos, and the public album/pull method signatures across Local Folder, Immich Photos, NextCloud Photos, and Google Photos were also aligned to tolerate the shared optional album-context parameters as no-ops for stronger cross-feature compatibility.
  • Fixed a regression in Automatic Migration introduced while adding per-album Album Pushed summaries. The new album-stat counters were originally wired through local helper closures, which could fail with NameError inside threaded puller_worker / pusher_worker execution in some runtime environments. Album summary counters are now updated through module-level helpers with explicit shared state, so threaded migrations no longer abort with _ensure_album_stats / _increment_album_stat lookup failures while building the final per-album summary line.
  • Fixed another Synology Photos Shared Space follow-up around issue #1173 by aligning the affected album-detail, album-list, item-list, count, and download requests with the browser-observed POST transport used by Synology Photos, while keeping GET as a compatibility fallback. Shared Space runtime album-detail hydration now also requests the same extra fields observed in the browser (flex_section and provider_count in addition to sharing_info and thumbnail), which helps keep owner-shared album classification and item discovery aligned with the real web client. (Issue #1173).
  • Fixed Automatic Migration similar-album consolidation confirmation for targets such as Immich. The consolidation path now reuses the same robust album-association verification flow already used by normal asset pushes, including confirmed-id tracking and follow-up membership refreshes, instead of relying on a single immediate album reread. This prevents false Album Consolidation Partial results such as repeated N-1 / N confirmed cases where the keeper album had actually accepted the missing asset but the simplified consolidation check undercounted it.
  • Fixed another Synology Photos Shared Space follow-up around issue #1173 where album-scoped item listings could still be emptied after retrieval by being revalidated against the global get_assets_by_filters() result set even when no explicit filters were active. Synology album listings now keep the assets returned by the album API unless real user filters must be applied, which avoids discarding valid Shared Space assets just because the global library listing exposes a different namespace than the album context. Also fixed Synology user-id normalization so owner_user_id=0 is preserved instead of being dropped, which keeps Shared Space owner metadata available for diagnostics and future classification logic.
  • Fixed the Web Interface Execution Output panel scroll handling after the incremental log renderer refactor. Horizontal scroll is now preserved while new log deltas arrive, reaching the bottom manually with the mouse wheel no longer forces an unexpected snap/repaint cycle, and re-enabling Auto Scroll now jumps reliably to the latest visible log lines instead of rebuilding a full snapshot unnecessarily.
  • Fixed an Automatic Migration regression in the Album Association Failed fallback cleanup path. Assets whose upload had already succeeded but whose destination album membership could not be confirmed were calling _finalize_album_association_failed_asset(...) with the newer shared finalization kwargs (asset_type, count_push_stats), while that helper still exposed the older narrower signature. The fallback cleanup path is now aligned to the new signature and additionally guarded so any internal cleanup/move error is logged as an album-association cleanup issue instead of incorrectly degrading an already uploaded asset to Push Failed. This prevents false Pushed + Failed double-counting for cases such as video assets inside localized special albums like Carpeta privada.
  • Fixed Local Folder initial file-type analysis so unsupported uppercase .MP files are now classified consistently as unknown / non-supported assets instead of being filtered inconsistently by suffix-only logic, and auxiliary JSON files such as progress.json are no longer counted as real metadata assets during the initial Takeout/local analysis.
  • Fixed Automatic Migration local-source asset selection so files already classified as unknown / unsupported (for example progress.json or unsupported .MP files) are no longer returned by the generic type='all' no-album scan and therefore are no longer pulled, staged, or pushed as if they were migrable assets. Also fixed the Local Folder no-album asset cache so results are now isolated per requested type instead of leaking a previous all query into later unsupported / metadata lookups.
  • Fixed the Web Interface Import Config flow so importing a .ini/.cfg/.txt configuration now preserves the original path values declared inside the imported file instead of rewriting them immediately to the active web user's allowed roots during import. Runtime execution still re-sanitizes effective path arguments per user as before.
  • Fixed Synology Photos owned-album listing for modules such as Remove Empty Albums by routing the SYNO.Foto.Browse.NormalAlbum -> list call through the same resilient entry.cgi transport fallback used by the newer Synology shared-space code paths, instead of relying only on the older direct GET request. Also fixed the associated error log so failed album-list responses now include the real Synology payload for diagnosis.
  • Fixed the Web Interface cloud-feature state handling so account-id is now persisted independently for each cloud module (Google Photos, Synology Photos, Immich Photos, NextCloud Photos) instead of being shared globally across all of them. Changing the selected account in one cloud feature no longer overwrites the account used by the others.
  • Refined the Web Interface Command Preview and matching execution command formatting so the visible command now uses a compact PhotoMigrator ... prefix instead of the full Python interpreter and .py launcher path, orders context-defining arguments first (--client, --account-id, --source, --target, main action flags), moves secondary album-normalization flags such as --consolidate-similar-albums and --prefer-canonical-album-names near the end before --configuration-file, and renders single-value options in --flag=value form for better readability while keeping multi-value options space-separated.
  • Refined the Web Interface command ordering again so both Command Preview and the real execution command now follow the same argument order as the upper Web Interface panels instead of a separate manual priority list. This also guarantees that --prefer-canonical-album-names is emitted before --consolidate-similar-albums whenever both are present, matching the order shown in General Arguments -> Execution.
  • Added another Synology Photos Shared Space diagnostic and recovery follow-up around issue #1173 for the remaining No Albums path. The global Synology asset listing used to derive assets without albums now emits targeted DEBUG summaries per request variant and after the final merge, including counts plus sampled id / filename / owner_user_id / provider_user_id values so mismatches between personal-space and Shared Space universes can be inspected from a normal debug log. In addition, the global asset scan now tries an extra browser-style SYNO.Foto.Browse.Item version=7 / method=list variant and merges successful results by asset id, while the downstream No Albums difference now also uses asset id instead of filename to avoid false matches when different assets share the same file name. (Issue #1173).
  • Fixed the extracted Automatic Migration Rich Live Dashboard failing on its first render with NameError: _compute_dashboard_estimated_time. The dashboard timing helpers now live with the terminal renderer and remain shared with the web snapshot path.
  • Fixed the GUI Stop button being disabled for Automatic Migration runs launched in an external Live Dashboard terminal. The GUI now tracks the external migration PID and sends the stop signal to that process rather than only tracking the terminal launcher.
  • Fixed Automatic Migration Live Dashboard startup after its renderer extraction. Its estimated-time calculation, UTC timezone dependency, background progress parser, and visible-progress-row selection now reside in LiveDashboard.py, preventing NameError failures while rendering or consuming tqdm progress lines.
  • Fixed the Rich Automatic Migration Live Dashboard layout so the Info Panel has enough height to render Assets in Queue, Delayed Retries Queue, and Album Assoc Queue together. Pull failure rows and Push 🔢 Total (New / Duplicates / Failed) summaries now remain on one line below their matching bars.
  • Aligned the Rich Automatic Migration Live Dashboard panels with the web layout: Blocked Albums and Blocked Assets now remain only in Info, the queue label uses a consistent-width timer emoji, and full-width separators now precede Info queues, Pull timing, and Push delayed-retry counters.
  • Fixed the macOS GUI external-terminal launcher for Automatic Migration Live Dashboard runs. PhotoMigrator now stays in the foreground terminal job while its PID is still reported to the GUI for Stop, preventing zsh suspended (tty output) / terminated job-control messages from shifting the final Rich dashboard.
  • Refined Rich Automatic Migration Live Dashboard panel alignment: the Push delayed-retry divider now has matching vertical spacing, both delayed counters use the same-width emoji, and the shared panel height was reduced after the layout fit was corrected.
  • Prevented Terminal.app zsh job-control suspension of the external Rich Automatic Migration Live Dashboard by disabling shell job monitoring before the foreground launch. Rich panel separators now also size themselves to their current panel width instead of overflowing fixed-length divider strings.
  • Fixed the Rich Automatic Migration Live Dashboard finalization and layout: GUI-launched dashboards now report migration completion back to the GUI before waiting for Ctrl+C, so final statistics remain visible while the GUI Run / Stop controls reset correctly. The completion prompt is shown inside the dashboard log panel, and the Info, Pull, and Push panel dividers are now rendered as full-width Rich rules instead of split table-cell fragments.
  • Fixed a Python syntax error in the POSIX external Live Dashboard launcher caused by escaped quotes inside an f-string expression.

📚 Documentation:

  • Updated documentation with all changes.
  • Expanded the Automatic Migration documentation to explain the current physical-file counter semantics, the meaning of each live dashboard counter, and how to interpret leftovers in Automatic_Migration_Push_Failed_*, especially the new Album Association Failed/<AlbumName> preservation path. Also updated the Web Interface documentation panels so Automatic Migration now lists --one-time-password under Optional arguments, and Google Takeout / iCloud Takeout now expose their feature documentation panel directly above the argument form.

💾 Download

Download the tool either for Linux, MacOS or Windows (for both x64 and arm64 architectures) or Docker version (platform & architecture independent) as you prefer, directly from following links:

Linux::

Mac OS:

Windows:

Docker Launcher:

Full Changelog: v4.4.1...v4.5.0