Quick Answer
Use Divi 5’s Preset Manager import/export control to move preset definitions in a JSON file between compatible sites. Treat the file as a design-system package, not a complete page or website backup. Review the destination’s existing presets and variables, then apply imported presets to representative elements before using them across live content.
A button style may be reusable across projects while its text, destination and surrounding layout remain project-specific. Preset transfer works best when the team records what the package is meant to supply.
What does a preset export contain?
The first-party preset import/export tutorial describes exporting preset definitions from the Preset Manager. Layouts, page content and templates are separate. The tutorial also demonstrates variables referenced by presets being carried into its destination site.
Record those dependencies rather than assuming every package is self-contained. Fonts, licensed images, custom modules and external resources can have their own installation and usage requirements. A JSON file containing a reference does not establish permission to use the referenced asset.
The design variable transfer guide covers the separate variable export and the content values that need special attention.
Export a named version of the preset library
Work from a known source site and confirm that its Divi version supports the documented controls. In the Visual Builder, open the Preset Manager, select its Import/Export icon and use Export to save a named JSON file.
Keep the source site, export date, intended use and required dependencies with the file. A name such as “service-site-components” is easier to understand than an unexplained “final” file. Record which person approves changes to the package.
Review business-specific content and asset references before sharing the file. A reusable visual style should not accidentally carry another organization’s identity into a new project.
Import into a controlled destination first
Review the destination library and preserve a recovery option before importing. Open its Preset Manager, choose Import and select the intended JSON file. Then inspect the resulting preset and variable lists.
Do not infer collision or replacement behavior from similar names. Check the actual result in the versions involved and record duplicates, renamed items or unresolved references. An imported library should be understandable to the person who will maintain it.
Apply a preset to a small test layout. Use actual content lengths, images and background colors representative of the destination. Review responsive values, hover and focus states, text readability and the HTML role where the preset includes one.
Check the component’s behavior in context
A preset can define shared presentation without deciding whether a control performs the right task. Confirm link destinations, labels and form behavior separately. A visually consistent button can still point to the wrong page.
For a reusable card, inspect at least a short and a long title, an image with a different aspect ratio and a case with missing optional content.
Check the semantic wrapper choices in presets before promoting a test component into a shared pattern. Its visual column position may not establish its document role.
Hand off the library with its limits
Document how editors select the approved presets and which settings they may override. Identify the shared presets that affect multiple pages. Explain how changes will be reviewed so an edit made for one page does not surprise another team member.
Keep the export alongside the design decisions and dependency list. It supports portability, while the site’s full recovery process remains responsible for content, files and database restoration.
Key Takeaways
- Preset exports transfer definitions rather than complete pages or templates.
- Record dependent variables, fonts, modules and asset rights.
- Inspect import results before applying presets broadly.
- Test real content variations and document shared editing rules.
Frequently Asked Questions
Is a preset export a full website backup?
No. It is a package of preset definitions. Preserve the separate recovery process for the site’s files, database, content and configuration.
Will imported presets look identical everywhere?
Check their dependencies and destination context. Fonts, variables, modules, content lengths and surrounding styles can affect the result.
Does importing presets also grant rights to referenced images or fonts?
No. Verify the source and permitted use of each dependency. A technical reference and a license are separate records.
For a reusable component library, include documentation and editor handoff in the WordPress design scope. Define future changes through ongoing development when needed.

