01 / The big one
Every Value, With the Layer It Came From
Open a module and read its values one by one, each labelled with its real origin and coloured by it. Seven origins, from the module default through to Custom CSS.
Built Natively for Divi 5
Divi Shows What.
This Shows Why.
Changed a preset, but a module still looks different? Divi Preset Inspector helps you trace the setting back to its source, find local overrides and review where your pages have drifted from the design system.
Submitted to the Elegant Themes Divi Marketplace. Awaiting review; not yet available for purchase.
$20 planned price Unlimited sites GPL licensed
- Visual Builder and dashboard only
- Nothing sent anywhere, ever
- Divi 5 native
Key Benefits
Find Overrides Before the Next Design Change
A page can look right while its modules use local values instead of presets. Find those differences before updating your colours or typography.
02
Find What a Preset Cannot Reach
Inline styles and Custom CSS can override the values you set in a preset. The inspector flags these sources so you can check the relevant declaration.
03
See Where Your Tokens Are Used
Colours and measurements typed by hand where a global colour or design variable already holds that value, counted per token, on one page or across the site.
04
Put It Back in One Click
Reset removes the local value so the preset shows through again. One value, one module, or the page. All of it undone by the builder's own undo.
How It Works
Open It, Scan, Reset What Should Go Back
No new workflow to learn and nothing to configure first. It sits on the toolbar you are already using.
-
Open It, Four Ways
The builder bar, a right click on any module, Divi's Command Center, or Cmd/Ctrl+Alt+P. Each one can be switched off, and the bar button carries a live count of what is covering a preset.
-
Scan the Page, or the Site
The panel reads the page you are editing across four views. The Overview screen reads every page, library layout and Theme Builder template on the site, a batch at a time.
-
Reset, or Take the Report
Reset the selected overrides through Divi's history, or use Generate Report to prepare a document you can save as a PDF. Review any site-wide changes separately before applying them.
Core Features
Eight Questions the Builder Leaves Open
Four views inside the Visual Builder, three screens in wp-admin, and one report that leaves with you.
Where Each Value Came From
Seven Origins, Each With Its Own Colour
This is what everything else is built on. Open a module and every value is listed with the layer that decided it, the ones beating your presets first.
- Hardcoded in Content: inline styling that can override preset values
- Custom CSS, one declaration at a time, by property
- Overridden: set here, and different from the preset
- Set Here: set on this module with no preset behind it
- From Preset: the one Divi applies when a group and a module preset collide
- Hidden Defaults: applied by Divi with no field default, so the input looks empty
- Source Not Read: when Divi will not hand over a group preset's values
A module, with the origin of every value it uses
This screenshot did not load.
Why the Preset Is Ignored
When a Preset Refuses to Change the Font
Check inline styles and the module's Custom CSS when a preset change has no visible effect. The panel lists the declarations it finds; CSS specificity and !important still affect which value wins.
style="..."attributes, one row per declared property<font>tags, one row each!importantanywhere in the content, reported as present- Custom CSS split into its real slots, not lumped together
- A warning when a free-form block restyles modules beyond its own
- When a declaration beats a real setting, the breakdown names the setting
Styling found in the content, and in the Custom CSS box
This screenshot did not load.
The Design System
Check Where Your Design System Is Being Used
Find and Replace takes a value, not a question: you have to know the hex before you can hunt it. This reads your global colours and design variables, then reports every value typed by hand that one of them already holds.
- Counted per token: “Primary Color, typed by hand 14 times”
- Exact matches and near misses counted apart
- Repeated values matching no token get their own list, named and left alone
- It never writes a token. Naming a colour is a design decision
The Design view, counting values your palette already holds
This screenshot did not load.
Three More Axes
Screen Sizes, Hover and Sticky, and Repeated Groups
Three more questions, answered from the scan already run. Each is a list with the modules named, because each is a judgement rather than a rule.
- Screen Sizes: settings decided on desktop with no answer on tablet or phone
- Hover and Sticky: values that appear only on hover or scroll, grouped by state
- Worth a Group Preset: a settings group repeated identically on four modules or more
Screen sizes, and the hover and sticky states
This screenshot did not load.
Consistency
Values That Disagree With Each Other
Four sections padded 40px, 45px, 40px and 50px. Two blues that differ in the last digit. Each is legitimate against its own preset. Together they are what makes a page look built by two people.
- Grouped by the setting they disagree about, with the gap and the count
- Four thresholds you set: minimum uses, number tolerance, a small-number floor, colour distance
- It never fixes them. A hero really might want 48px
- The whole view switches off if it is not a question you want asked
The Consistency view, where a page disagrees with itself
This screenshot did not load.
The Whole Page
The Page as Divi's Own Hierarchy, Branch by Branch
Structure draws the page the way the builder does, one level at a time. Findings is the same page sorted by how far each module has drifted.
- Open a module's row and its breakdown appears inside it
- Show Me scrolls the canvas to the module and marks it
- Open lands on the settings group that owns the value
- Why shows the layer waterfall behind that one value
- Preset Impact counts the modules on a preset and the ones that have drifted
- A real Divi modal: drag, snap, dock and resize, in Divi's own accent and colour modes
Structure and Findings, the page as Divi's own hierarchy
This screenshot did not load.
Reset and Alerts
Reset Removes the Local Value, and Nothing Else
Copying the preset value onto a module leaves it just as detached, and the next preset edit still will not reach it. Removing the local value is what puts it back under the preset.
- One value, every override on a module, or every override on the page
- Every reset goes into Divi's own history, so the builder undo reverses it
- Clear for Preset removes everything a preset would otherwise decide
- Drift alerts appear on the canvas the moment a preset value is overridden
A drift alert on the canvas, with a one click reset
This screenshot did not load.
The Whole Site
Every Page, in One Pass
Overview finds every piece of Divi content, including the parts a page list leaves out. Design Audit is the second screen, asking about the design system rather than any one page.
- Pages, posts, library layouts, Theme Builder templates and global canvases
- Filters for overriding a preset, hardcoded styling, off the design system, and clean
- Open in Builder on every row, so the fix is one click from the finding
- Design Audit: every global colour with a usage count, near-duplicates and the unused
- The full preset inventory, including the ones nothing uses
- Anything still holding Divi 4 shortcodes, which loads the Divi 4 framework alongside Divi 5
The Overview screen, after a scan of the whole site
This screenshot did not load.
The Design System Itself
A Preset Can Be Applied and Still Do Nothing
Everything above answers why a module looks the way it does. This answers whether the design system underneath it is still whole.
Missing References, on the Design Audit screen
Screenshot coming with this release.
The Snapshots screen, and what the last change did
Screenshot coming with this release.
01 / The one people report
Why the Preset Did Nothing
A preset whose own record is incomplete produces styling under a name that matches nothing on the page: assigned, rendered, and unable to change a thing. Every preset on your site is checked, and the ones that cannot work are named with the reason.
02
References That Point at Nothing
A preset can hold a colour or a design variable that is no longer there, and Divi says nothing about it. Every reference on the site is resolved, with the number of pages affected beside each one.
03
A Copy of Your Design System
Your global colours, design variables and presets are copied whenever Divi rewrites them, and so is the state a change was about to replace. If a variable disappears you are told which one, and when.
04
Put It Back
Any copy can be restored. You are shown exactly what would change before anything is written, and a copy of the current state is kept first, so the restore is undoable in turn.
05
Check the Live Page
Right in the builder and wrong on the site is a real thing, and hard to prove. One button asks for a page the way a visitor would and reports the presets that arrive with no styling behind them.
06
Connect a Value Everywhere
Divi's Find and Replace works on one page at a time. This connects a value typed by hand to the colour or variable that already holds it, across every page, layout and template at once. The list is shown before anything is written.
Templates and Library Too
Theme Builder templates, library layouts and global canvases are scanned like anything else. Divi's own Find and Replace stops at the page you have open.
What the Divi 4 Migration Left
Divi's own converter pins every section, row and column it migrates to the block layout Divi 4 had. Those are counted so you can find them, and not called a fault: block may be exactly what you want.
See It in Action
Watch the Whole Thing, End to End
Watch the inspector in the Visual Builder, see how styling sources are reported, and follow the available tools for reviewing and correcting overrides.
Use Cases
When a Preset Change Does Not Show Up
Start with the module that looks wrong, or scan the site when you need a broader view.
Find the Value That Is Overriding Everything
You changed the preset and one button stayed the same colour. Open the module and the panel names the layer beating it, whether that is the module, its Custom CSS, or a span buried in the text.
Check the source before changing another setting.
Inherit a Site and Find Out What It Is Made Of
Scan the whole site before you quote the work. Pages worst first, presets nothing uses, near-duplicate colours, and any content still dragging the Divi 4 framework along behind it.
Use the findings to scope the cleanup.
Make a Palette Change Actually Reach the Page
A colour typed by hand does not follow when the palette changes. The Design view counts them, names the global colour each one should be, and points at Divi's Find and Replace to swap them at once.
Find hand-entered colours that will not follow a palette update.
Why Choose Divi Preset Inspector
Where Every Value Came From
It Reports, and Points at Divi's Own Controls
Where Divi already ships the tool, this does not build a second one. Preset Impact names Divi's Update Preset button; the design system findings end at Find and Replace.
Built Around Divi's Styling Layers
Review module values, presets and Custom CSS in one place, then use the relevant controls to make a change.
| Capability | Divi Preset Inspector | Native Divi |
|---|---|---|
| See which layer a value came from | Yes Every value | No The result only |
| Find styling hardcoded into content | Yes | No |
| Read Custom CSS as a layer | Yes By declaration | No |
| Find values a global colour already holds | Yes Counted per token | No Only if you know the value |
| Find values that disagree with each other | Yes Yes, with thresholds | No |
| Find settings with no answer below the desktop | Yes Counted per setting | No |
| Reset back to the preset | Yes Value, module or page | No By hand, per field |
| Warn when a preset value is overridden | Yes On the canvas | No |
| Scan the whole site | Yes Pages, layouts, templates | No |
| Find unused presets and near-duplicate colours | Yes Across the site | No |
| Printable report | Yes Page or site | No |
Performance and Privacy
What the Plugin Loads and Stores
Three answers, all of them checkable on your own install.
The Settings screen, with every switch on it
This screenshot did not load.
The Design Audit screen, the design system itself
This screenshot did not load.
01 / What it loads
Inspection Tools Stay in the Builder and Admin
The inspector does not add a public-facing module or visitor stylesheet. Settings and design-system snapshots are stored in WordPress options. Site scans and changes still use server resources; this is not a guarantee of unchanged performance scores.
02 / What it sends
No Tracking or Licence Server
The plugin does not include analytics or a licence-server check. The live-page check requests a page from your own site when you run it, so it can compare the output with the builder data.
03 / What it writes
It Reports First, and Asks Before It Writes
Most of it only reads. Reset goes into Divi's own history, so the builder undo reverses it. Connecting a value across the site shows every page it would touch first. The settings screen is for administrators, and the panel follows the builder access Divi already grants.
Pricing
Planned Pricing
Planned at $20 for use on unlimited sites. The product is awaiting marketplace review; final purchase and support terms will be confirmed at launch.
$20one time
Planned as a one-time purchase. Update access and support terms will be confirmed on the approved listing.
- Every feature from install. Nothing is gated behind a tier
- No licence key and no activation step
- GPL licensed, so use it on as many sites as you build
- Update and support terms confirmed at launch
- Works on client sites, and stays working if you hand the site over
Awaiting Elegant Themes Marketplace review. Purchases and pre-orders are not open. Pricing and final terms will be confirmed at launch. What the purchase covers.
Buying, Licence and Support
Everything Around the Purchase, in One Place
The intended sales channel is the Divi Marketplace. The plugin is still awaiting review, so purchases are not open.
Payment
If approved, purchases will go through the Divi Marketplace. We are not taking payments or pre-orders.
Licence
The plugin is GPL-2.0-or-later and is planned for use on unlimited sites. Check the approved listing for update and support terms.
Refunds
If the product is approved, check the marketplace listing and service policy for the applicable refund terms before purchasing.
Support
Contact StackVane HQ with questions about setup or compatibility. Support terms for purchases will be confirmed at launch.
FAQ
Frequently Asked Questions
No. It reads Divi 5's resolution order through Divi 5's own APIs, and Divi 4 has no equivalent. It does report Divi 4 content it finds on a Divi 5 site, because one legacy module loads the whole Divi 4 framework alongside Divi 5.
Inspection reads your settings. Reset changes a module value through Divi's history, and Connect previews the affected content before applying changes. Restoring a design-system snapshot also writes data. The plugin stores its settings and snapshots in WordPress options.
That sentence has more than one cause, and each is checked: something on the module sitting on top of the preset, inline styling in the text, the module's Custom CSS box, a preset asking for a colour that no longer exists, an incomplete preset record, or a stylesheet built before your last change. Each is reported as itself, with the reason.
Yes, within what it has copied. Your global colours, design variables and presets are copied whenever Divi rewrites them, and so is the state a change was about to replace. Restoring shows what would change first and keeps a copy before it writes. It copies the design system only, not your pages.
No, and they sit on the same toolbar. Divi's Inspector shows the rendered CSS a module produced. This shows which of your own layers decided each value: the module default, the preset stack, a group preset, the module itself, or Custom CSS.
Once available, upload the ZIP under Plugins › Add New › Upload Plugin and activate it. Check the approved listing for update access and support terms.
Releases
Version Notes
The version below has been submitted for review. Its notes are also included in the plugin readme.
- Version submitted to the Elegant Themes Divi Marketplace. Public availability is pending review.
- Requires Divi 5, WordPress 6.0 or later, and PHP 7.4 or later.
You May Also Like
Two More Tools for Divi 5
Same GPL licence and the same people, and one of them is free. Each one does a single job the builder leaves to you.
Divi Optin Extended
Available on Divi Marketplace
Add content reveals, store coupons, signed download links, account creation or automation to the Divi 5 Email Optin module.
See Divi Optin ExtendedStackVane Video Import for Divi
Available on WordPress.org
Divi’s Video Slider takes one slide at a time. StackVane adds a Bulk Import button to the module you already use: paste a list of URLs, pick from your Media Library, or drop in a whole YouTube playlist.
See StackVane Video Import for Divi
Ready When You Are
Stop Guessing Which Layer Is Winning
Explore the walkthrough, or sign up for an update when Divi Preset Inspector becomes available.