Yes. The standard Smush postmeta keys are written by both the free plugin and Smush Pro, so SleekView's columns and filters work the same way on either tier. Pro features such as super-Smush savings, lossy compression metadata, the CDN status, and the directory Smush tool surface as additional columns automatically when Pro is active.

Yes. SleekView calls Smush's own optimize function from the inline action, so backups, CDN sync, and the directory log behave the same as a Smush triggered from the bulk screen. The bulk action selects multiple rows at once, which is useful for clearing a backlog after enabling super-Smush or after raising the size threshold.

Yes. Smush records WebP conversion status per attachment when the WebP module is active, and SleekView surfaces that as a boolean column. A saved view of attachments missing WebP makes it easy to fill coverage gaps after enabling WebP on an older library that was originally optimized in JPEG and PNG only.

Yes. Smush Pro can optimize images outside the standard media library through its directory Smush tool, which records progress in its own data. SleekView registers that data as a separate source so theme images, plugin assets, and other non-attachment files appear in their own view next to the standard attachment view.

Yes. The dashboard view summarises total bytes saved and average percentage saved, the same figures the Smush dashboard shows. A grouped view by upload year or by post type breaks the totals down so editorial leads can see which sections of the site benefit most from a focused round of optimization.

No. SleekView reads the lazy load eligibility flag Smush sets on each attachment and surfaces it as a column. The actual lazy loading continues to be handled by Smush itself, and turning lazy load on or off for an attachment from the table calls Smush's own toggle so the front-end behaviour matches the plugin's settings.

No. SleekView paginates against the standard postmeta indexes and only loads the visible page. Heavy filters resolve in the database the same way Smush'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 Smush's own restore function, which pulls the original from the backup folder and updates postmeta accordingly. SleekView never touches backup files directly; the backup folder and the Smush log remain authoritative, with SleekView simply exposing the action next to the row that needs it.