Yes. Imagify free, the monthly subscription tiers, and the Imagify Infinite plan all write the same postmeta on each attachment. SleekView reads that postmeta regardless of plan tier. Quota usage in the dashboard view shows the remaining monthly credit and updates whenever Imagify itself refreshes it.

Yes. SleekView calls Imagify's own optimize function from the inline action, so quota accounting, backups, and the optimization log behave exactly as a re-run from the bulk screen. The bulk action selects multiple rows at once, useful for re-running on Ultra after a level upgrade or for retrying a batch that hit a transient error.

Yes. Imagify records WebP coverage per attachment, and AVIF when the AVIF feature is active on Pro plans. SleekView surfaces both as boolean columns. A saved view of attachments missing AVIF makes it easy to fill format gaps after enabling AVIF on a library that was originally optimized to WebP only.

Imagify primarily optimizes attachments inside the standard media library. Other-files support depends on the active integrations (custom folders, theme images). Where Imagify writes optimization data for those files, SleekView surfaces them as their own filtered view alongside the standard attachment view.

Yes. The dashboard view summarises total bytes saved and average percentage saved, the same figures Imagify's dashboard shows. A grouped view by upload year, post type, or author breaks the totals down so editorial leads and performance teams see the slice that matches their reporting cadence.

No. SleekView reads the postmeta and queue state Imagify already maintains. The bulk optimize process continues to run on its own schedule. Inline re-optimize calls hand off to the same functions the bulk screen uses, so quota accounting and queue management stay consistent.

No. SleekView paginates against the standard postmeta indexes and only loads the visible page. Heavy filters resolve in the database the same way Imagify's own admin queries do, and saved views do not pre-fetch anything until they are opened, so the WP admin stays responsive on libraries of any size.

Yes. The restore action on a row calls Imagify's own restore function, which pulls the original from the backup directory and updates the postmeta accordingly. SleekView never touches backup files directly; the backup directory and Imagify's log remain authoritative, with SleekView just exposing the action where the row already lives.