VeriRelay

VeriRelay moves eligible WordPress Media Library files to supported remote storage without moving the WordPress site itself.

The normal workflow is intentionally short:

• Connect remote storage.

• Copy and verify media.

• Enable public/CDN delivery and visually confirm the site.

• Reclaim local disk space through guarded cleanup.

The safety engine remains active behind the simple wizard. Files are copied before local cleanup, remote copies are verified, additional files in standard WordPress year/month upload folders are detected and protected, a small cleanup pilot is required, and every local file is checked again against its remote copy immediately before deletion.

After historical cleanup, new attachments are automatically copied and verified. After a configurable grace period, their local copies can be removed automatically so local disk usage does not grow back.

Plugin-owned or non-standard upload directories are excluded from automatic cleanup unless a compatible workflow explicitly handles them.

express.

Features

• Four-step migration wizard for normal use.

• Copy-before-delete workflow.

• Remote existence and size verification.

• Public/CDN delivery without database-wide URL replacement.

• Compatibility for historical WordPress year/month media URLs.

• Detection and protection of additional files in standard upload folders.

• Required 50-file cleanup pilot before full historical cleanup.

• Resumable guarded bulk cleanup.

• Emergency restore plan retained after historical cleanup.

• Safe-deactivation workflow that restores remote-only media locally before CDN delivery is disabled.

• Automatic offload for newly uploaded media after a grace period.

• Advanced diagnostics and restore tools separated from the normal workflow.

• WordPress HTTP API for outbound storage requests.

• WordPress Filesystem API family for local media writes and removals.

• Compatibility migration for earlier internal beta/RC state.

• Internationalization-ready source strings for WordPress.org language packs.

External services

This plugin connects to an external storage service only after an administrator configures storage credentials and starts the offload workflow.

express. When configured, eligible WordPress media files are transmitted to the administrator’s storage account. The plugin also sends authenticated API requests to create directories, check file existence and size, upload files, and remove temporary test files or other remote files only when an explicit supported workflow requires that remote action.

Public media is then served from the public storage/CDN address configured by the administrator.

ua

ua/

ua/legal/privacypolicy/

ua/legal/

Storage credentials are provided by the site administrator and are not sent to the plugin author.

Privacy

VeriRelay does not create an account with the plugin author and does not send analytics or telemetry to the plugin author. Media files and storage API credentials are used only to perform storage operations configured by the site administrator.

Because media files may contain personal or confidential information, administrators are responsible for determining whether their chosen external storage provider is appropriate for the content they offload and for complying with applicable privacy, contractual, and data-protection requirements.

Deactivation and uninstall safety

A site with remote-only media can depend on VeriRelay for runtime URL delivery. Before permanent deactivation, use the main-screen “Prepare for deactivation” action. Automatic local deletion stops first; recoverable remote-only media and files from the retained historical cleanup plan are restored locally and size-verified; CDN delivery is disabled only after the restore succeeds.

Normal deactivation keeps settings so the plugin can be reactivated without reconfiguration. Deactivation also clears the plugin’s pending automatic-mirror schedule.

The plugin intentionally does not delete remote media as part of deactivation or uninstall. If uninstall occurs after the site has reached the explicit safe-to-deactivate state, local plugin options/state and VMOFF attachment metadata are removed. If uninstall is attempted without that safe state, recovery configuration is intentionally retained in the database so reinstalling the plugin can still recover the setup.