WP Time Capsule's whole pitch is incremental backups: rather than building a fresh archive every night, the plugin tracks the files and database rows that changed since the last run and ships only the diff to a third-party destination like Google Drive, Dropbox, Amazon S3, or Wasabi. The metadata for each run, the changed files, the rows touched, the destination, the duration, the outcome, lives in the plugin's own tables and option records.

The default WP Time Capsule admin renders the calendar view that is the plugin's signature feature, with daily snapshots represented as dots on a timeline. The calendar is excellent for picking a date to restore from, but it is the wrong UI for asking which destinations failed last week, which runs took longer than usual, or how the size of incremental diffs has trended over the last quarter. Those are table questions, and SleekView reads the same WP Time Capsule metadata as a flat, sortable grid.

One row per run shows the date, type (Files, Database, Full, Snapshot), destination, the number of changed files or rows, the diff size, the duration, and the outcome. Filter to runs with diffs over 500 MB to find the surprisingly heavy days. Filter to status Failed and sort by date descending to find the last issue. Restore points (the named snapshots WP Time Capsule lets you tag before a deploy) become a column you can filter, so the safe restore source is always one click away.

WP Time Capsule picked an unusual position in the WordPress backup market: incremental, third-party-destination only, calendar-first. That position is exactly right for sites where a full nightly archive is wasteful (because most of the site has not changed) and where a calendar of snapshots is the natural way to think about restoration. The trade-off is that the calendar UI is poor for asking ops questions across many runs.

Was Wasabi slow last week? Did the diff size double after the last theme rebuild? Which days had zero changed files and should have been near-instant runs but took fifteen minutes anyway? Those are table questions, and the calendar cannot answer them. SleekView reads the same WP Time Capsule run records as a flat grid, joined on date, type, destination, and outcome. The calendar stays where it belongs, as the restore tool, and the operational health of the schedule finally has a query surface.

For sites that picked WP Time Capsule for the incremental model, that operational surface is the missing half of what a backup workflow needs.