Yes. SleekPixel reads the cptui_post_types option that CPT UI writes to and lists each registered post type in its admin. You assign a template per post type from there, and SleekPixel hooks into save_post_{post_type} for each one.

Yes. That is the main reason this integration exists. A portfolio CPT can get a project-card template, a recipe CPT can get a recipe-card template, and a property CPT can get a listing-card template. Each template maps to that CPT's specific fields and registered taxonomies.

Yes. SleekPixel calls get_object_taxonomies() for each CPT and exposes every registered taxonomy as a variable in the template editor. Terms render as badges, footer labels, or category lines without extra configuration.

It shows up in the SleekPixel admin the next time you reload, since SleekPixel re-reads the CPT UI option on every admin page load. You can assign a template at that point. Existing entries are picked up by the bulk regenerate command for that CPT.

Yes. Any postmeta key written to wp_postmeta against a CPT entry can be mapped into a template slot. If you use ACF, Meta Box, or hand-rolled meta boxes alongside CPT UI, those keys appear as available variables once the template detects them on a sample entry.

Real files. Each CPT entry's card is generated server-side on save and stored in the uploads directory as a PNG, then attached to that post. The og:image tag points to the static URL, so social platforms cache the image like any other featured image.

Yes. SleekPixel ships a WP-CLI command and an admin action that walks every entry of a chosen post type and regenerates the card in batches. The job runs as a background queue so it does not block the admin while a portfolio of 800 entries refreshes.

Yes. SleekPixel does not require CPT UI specifically. Any registered post type, whether created via CPT UI, Post Types Unlimited, ACF, or a plugin's own register_post_type call, appears in the SleekPixel admin and can have a template assigned to it.