Yes. Both versions use the same wp_wpdatatables table for definitions and the same shortcode format. Pro-only source types like MySQL, Google Sheet, and Excel surface as badges in the SleekPixel card. Lite-only manual tables also work, they just show as 'manual' source.

wpDataTables charts are stored as their own entries linked to a table. SleekPixel parses [wpdatachart id=N] embeds separately, reads the chart's title and the linked table, and composes a card that names both. The chart type, line or bar or pie, can be reflected as a small icon on the card.

Yes when the wpDataTables cron syncs the view, which fires its own refresh action. SleekPixel hooks that action and regenerates the card for every post embedding that table id, with the new row count and new refresh timestamp.

Yes. The first data row and any specific cell are template fields. You can render the top row as a typographic preview, or pin a specific cell like the latest total, which is common for dashboards where one summary number drives the story.

Google Sheets refreshes work like any other source. The refresh interval is stored on the wpDataTables entry and surfaces as the badge or footer line on the card. SleekPixel does not call Google itself, it reads the cached result from wpDataTables.

No. Regeneration runs asynchronously through WordPress's cron or Action Scheduler. The refresh itself completes immediately and the OG image rebuilds in the next queue tick, usually within seconds, with no blocking on the data import.

Yes. MySQL-backed tables can use a warehouse-themed template while manual tables can use a static-content template. The wpDataTables source-type field is exposed as a routing field, so the right template is picked automatically per table id.

In wp-content/uploads/sleek-pixel/ on your own server. Your existing CDN handles delivery. No external SleekPixel service is in the path, no per-render fees, and the og:image URL points to your own domain.