SleekPixel for Duplicator deployment packages
Duplicator builds a single-archive installer for moving a WordPress site between environments. SleekPixel reads the duplicator_packages table for the package being shared, then renders an OG card showing the archive size, installer state, table count, and source environment on the card surface.
♾️ Lifetime License available
Deployment URLs that show the package details up front
Duplicator (Snap Creek / Awesome Motive) stores its package catalogue in a custom table called wp_duplicator_packages with columns for package hash, name, status, created timestamp, owner, and a serialised manifest containing the archive size, database details, and installer metadata. Built packages live in wp-content/backups-dup-lite/ (or backups-dup-pro/ on Pro) and the public download URL combines the hash with the archive extension.
Agencies running Duplicator share package URLs in Slack for deploy handoffs, in email for client environment delivery, and in runbooks for repeatable migrations. The default share preview is the source site's homepage card, which carries no information about the package itself. Migration handoffs start with a click-through to confirm the right hash, and on-call engineers paged about a rollback have no preview cue about which package the runbook is pointing at.
SleekPixel reads the duplicator_packages row for the URL being scraped, then composes a card with the package name, hash, archive size, database table count, installer state, and source environment. Failed builds render with an amber template; in-progress builds show the current step pulled from the package status.
Workflow
From packages table to share card
Apply to package URLs
Bind package row fields
wp_duplicator_packages: name, hash, status, created timestamp, owner. Manifest fields (archive size, table count, components) come from the serialised payload in the row data.
Hook build completion
Share package URLs
Output
Sample Duplicator package card
Rendered from a real wp_duplicator_packages row showing package hash, archive size, table count, and installer state for a manual production build.
Comparison
Default deploy OG vs SleekPixel for Duplicator
Same source-site logo
- Every Duplicator package URL previews with the source site's homepage image
- Package hashes and names from the duplicator_packages table never reach previews
- Build status (in progress, failed, ready) stays invisible at share time
- Archive size and table count remain hidden until someone opens the page
- Deployment handoffs cannot confirm the right package from chat alone
SleekPixel
-
Reads
wp_duplicator_packagesfor the package row by hash or row ID - Package name and short hash combine on the card headline area
- Archive size and database table count composited from the manifest payload
- Status badge: Ready, Building, Failed, Stored, Cloud-uploaded indicators
- Source environment label drawn from the package owner site URL field
Features
What SleekPixel gives you for Duplicator
Package name and hash
The package name and short hash render as the card headline. Long auto-generated names from Duplicator (date-stamped with environment) make recognition easy at a glance, and the hash disambiguates packages built within the same minute on busy deployment days.
Database and archive metrics
The card surfaces archive size in human-readable units and the total database table count from the manifest. Migration teams use both numbers to estimate import duration on the destination environment before triggering the installer to start its work.
Build status badge
Ready packages render with the success accent. In-progress builds show a Building badge with the current phase. Failed builds render in amber with the failure step visible. The card communicates state at share time without anyone opening the dashboard at all.
Use cases
Where Duplicator cards earn their place in deploys
Scheduled production deploys
Deploy URLs paste into release channels with the package name, hash, and size already on the preview. The receiving engineer confirms the right build before pulling it down to the target environment.
Rollback package custody
Pre-deploy rollback packages shared in runbooks render with creation timestamp and source environment on the preview. Months later, the right rollback is findable from the runbook in seconds.
Project delivery handoffs
End-of-engagement package URLs forwarded to clients arrive with size, scope, and source on the card. Clients see evidence the package is real and complete without needing technical tooling first.
The bigger picture
Why Duplicator cards prevent deploy mistakes
A wrong-package deploy is one of the most reliably painful incidents an agency can cause. Duplicator makes packaging easy, which is exactly the danger: a team that builds packages routinely also has lots of packages floating around, and any one of them can be the wrong one to deploy. The hash and name are visible in the dashboard, but the dashboard is not where the conversation happens.
The conversation happens in Slack, in email, in runbooks. Default link previews show the source site's homepage for every package URL, which means a Tuesday rollback build and a Friday cleanup build look identical until someone clicks. SleekPixel reads the package row Duplicator already writes and composes a card that names the package, surfaces its hash and size, and communicates its status.
The deployment team can verify at preview time that they are pulling the right archive.
Questions
Common questions about SleekPixel for Duplicator
Yes. Both versions write to wp_duplicator_packages with the same column structure. Pro adds remote-destination fields (S3, Google Drive, Dropbox, OneDrive) that SleekPixel can optionally render on the card alongside the local package details.
Partially. Duplicator updates the package status as the build moves through phases (archiving database, archiving files, building installer). SleekPixel can render a Building card with the current phase, though social scraper caches will lag the live state by minutes.
Yes. Pro records cloud-upload destinations in the package row. SleekPixel surfaces those destinations as small icons (S3, Google Drive, Dropbox, OneDrive, FTP), so the card communicates the full storage footprint of the package not just the local copy.
The row stays in wp_duplicator_packages even after the archive file is deleted, with a status flag indicating absence. SleekPixel renders an Archive removed card so the URL signals that the package is no longer available for download without misleading recipients.
Yes. The package row includes the owner and trigger source. Manual builds can render with the user who triggered them, scheduled builds with the schedule name, and multisite-network builds with the network identifier. Each variant pulls from the same row.
Yes. Pro supports network packages, and SleekPixel renders a multisite variant with the sub-site count and network name on the card. The base table-count and archive-size numbers still come from the same package row, with the multisite flag driving the layout branch.
No. Card regeneration runs after the build-complete hook fires and takes maybe a second of work via Action Scheduler. The actual archive build (database export, file collection, installer assembly) is completely untouched by SleekPixel during the run.
Yes. Duplicator computes hashes for the archive and the installer. SleekPixel can render either or both as a small fingerprint on the card, useful for security-sensitive deploys where the receiving team wants to verify integrity before running the installer.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- YouTube Shorts covers
- YouTube channel banners
- Warpcast frame images
- TikTok shop images
- Twitch profile banner
- WeChat Moments images
- Twitch camera frame
- Threads story-style images
- Linktree banner image
- TikTok cover images
- LinkedIn company banners
- Vimeo channel banners
- Beacons.ai banner
- Mastodon post images
- Rumble thumbnails