Yes. Both versions write to the same wpvivid_backup_list option structure. Pro features like staging-site backups and incremental runs add fields that the template can optionally render, but the base integration works on either tier without configuration changes.

Yes. The destination field in each backup entry tells SleekPixel where the archive lives. The card renders the destination icon and the location label. The image itself stays hosted on the WordPress site, only the backup file lives remotely.

If the entry disappears from wpvivid_backup_list, the URL falls back to a generic site card on the next regeneration. Stale share previews continue showing the old card until scrapers re-fetch, at which point they pick up the fallback.

Yes. WPvivid stores split sizes for database, uploads, plugins, themes, and core. The template renders the two largest components (typically DB and uploads) as paired numbers, with a Total prominent above them. Smaller components show on hover or expanded view.

No. Card regeneration runs after wpvivid_backup_complete fires and adds maybe a second of work post-completion. The backup process itself, including the upload to the remote destination, is untouched. Image rendering happens in the background via Action Scheduler.

Yes. Scheduled migrations write entries to the same backup list with a migration flag set. The template can branch on that flag to render a migration-specific card with source and destination site URLs instead of just a backup ID.

Yes. The template accent, logo, and copy are all configurable per site. Agencies running WPvivid Pro under their own branding can drive the card's surround from their agency brand while keeping the backup-specific data in the centre identical.

No. SleekPixel only reads the backup-list option to get metadata, then renders a PNG card. The archive files themselves, whether stored locally or pushed to a remote destination, are never opened, modified, or moved by the integration in any way.