Yes. Both versions write to the same option keys (updraft_last_backup, updraft_backup_history) with the same field structure. Premium features like incremental backups and multisite handling add fields the template can optionally render.

Partially. UpdraftPlus stores progress in transients keyed by job ID. SleekPixel can render an In progress variant of the card with the current step (Backing up uploads, Uploading to S3), but the social scraper cache means the visible preview lags behind the live state.

Once a backup ages out of the history, the entry disappears from updraft_backup_history. The URL falls back to a generic site card. Old share previews continue showing the historical card until scrapers re-fetch, at which point they pick up the fallback.

Yes. UpdraftCentral controls backups remotely but the local UpdraftPlus history is still the source of truth on each site. Cards render from the local history regardless of whether the backup was triggered locally, on a schedule, or via UpdraftCentral.

Yes. The job entry includes a flag for the trigger source. Scheduled backups can render with the schedule name (Nightly, Weekly), manual backups with the user who triggered it, and incremental backups with a chain reference to the previous full backup.

Yes. Premium can upload one backup to multiple destinations. SleekPixel renders all configured destinations as icons (Google Drive plus Dropbox plus S3, for instance), so the card communicates the full redundancy picture not just the first destination.

No. Card regeneration runs after the updraftplus_backup_complete hook fires and takes maybe a second of background work via Action Scheduler. The backup itself, including database export and remote upload, is completely untouched by SleekPixel.

Yes. If UpdraftPlus Premium encrypted the archive, the job entry records that. SleekPixel can render a small lock icon and an Encrypted label, signalling to the recipient that the archive cannot be restored without the corresponding key.