FrameQuery 1.2.6: Faster Backups, Reliable Shared Indexes

FrameQuery 1.2.6 makes FQ Cloud shared indexes reliable from the first upload through every subscriber download. It also creates backups faster with lower peak memory use and improves recovery for large libraries.

What's new in 1.2.6

Reliable shared-index publishing: uploads use the exact archive prepared by FrameQuery, report accurate progress, and verify the published file before completing.
Dependable subscriptions: subscribers download the correct published archive, and installed subscriptions keep working after a restart.
Faster, leaner backups: backup creation spends less time and memory packing thumbnails and other library files, with better handling for large manifests.
Clearer backup controls: progress is easier to follow, and an in-progress backup can be cancelled from its status row.
Stronger recovery: thumbnail restoration and compatibility with large backup archives are improved.
Clearer FQ Cloud access: access-code examples match the current eight-character format. Free accounts see the Starter upgrade path while local index imports remain available.

Shared indexes that arrive intact

Publishing an index now tracks one archive from creation through upload and server verification. The progress bar follows the active publish operation, stays monotonic, and reaches 100% only after the upload succeeds.

On the receiving side, FrameQuery validates the downloaded archive before installing it and accepts the authenticated local files it creates after installation. That keeps the strict checks on downloaded content without breaking a healthy subscription on the next launch.

If you share an index through FQ Cloud, existing access codes continue to work. New code examples now use the same eight-character format shown by the service.

Backups for bigger libraries

Backup creation now avoids unnecessary database preparation work and packs image-heavy folders more efficiently. This reduces peak memory use and can substantially shorten the packaging stage, especially in libraries with many thumbnails.

Large archives use ZIP64-compatible handling, and restore validation now covers thumbnail data more reliably. The backup row also keeps the current operation visible and offers a direct Cancel action while packaging is underway.

Fixes

Shared-index uploads could finish against a different object key than the one subscribers were given.
Publish progress could jump backwards or be overwritten by an older operation.
A downloaded shared index could pass validation, then be rejected after FrameQuery created its local search files.
Shared-index subscriptions could fail to reopen after restarting the app.
Backup packaging could use excessive memory when a library contained many images.
Large backup archives and thumbnail restoration had avoidable compatibility gaps.
Free accounts were offered an FQ Cloud join flow they could not complete instead of the Starter upgrade path.

How to update

FrameQuery checks for updates on launch, or download for macOS (Apple Silicon) and Windows from the download page. Your local libraries do not need re-indexing. Publishers should keep the app open until the shared-index progress reaches 100%.