Divi Library Imports: Match the Item Type to the Destination

By Dave TanguayPublished Updated Editorial draft

Quick Answer

Match a Divi Library item’s type to its intended destination before importing it. A full page layout, section, row and module use different insertion routes. Review whether existing page content will be replaced and whether the file brings linked components or shared styles. Test the exact import on a protected copy and inspect what arrived.

A preview image can hide the scope of a library file. A design that looks like one section might be packaged as a complete layout. Read the item’s actual type before choosing where it belongs.

Name the destination and the content to preserve

Record whether the work concerns a page body, a section within it or a separate Theme Builder area. Preserve the existing content and template assignments before an authorized import. Decide whether the imported material should replace a whole composition or supply one element.

The official Divi 5 Library import guide identifies four item types and their insertion routes. Use the guide for the installed version; a generic JSON filename does not identify the right import context.

Match the library item to its container

Library item Destination decision
Full page layout Use the page-layout route and decide explicitly whether to replace existing content.
Section Insert through the section’s Add From Library route at the intended page location.
Row Use the row route inside the intended section.
Module Use the module route inside the intended row.

For a full page import, the cited guide says to leave Replace Existing Content unchecked when retaining the current layout. Verify that choice in the actual workflow before confirming it. A section import and a full page replacement are different operations.

Review linked components and shared dependencies

The current Components Manager guide explains that exported page layouts include components they use, including nested components. Its Import Components option is checked by default.

The guide also describes reusing an existing component when its name and element type match during component import. Review the actual references and resulting behavior; do not assume an imported element is an isolated copy because it appears inside one page.

Record components, presets, colors or variables involved in the trial. If an element arrives without a component match, inspect its resulting regular-element state. Keep the source file and the accepted import distinguishable.

Run one controlled import and inspect the result

Use a protected development copy and confirm the destination before importing. Record the selected item type, replacement choice and dependency options. Afterward, inspect the structure in the builder and the rendered page.

Check that required existing content remains, the item sits in its intended container and linked references behave as expected. Verify another affected location if the import reuses shared definitions. Restore the trial if it does not match the approved scope.

The layout adaptation guide covers replacing demonstration content and adjusting styles. The grid resource guide covers a specific collection’s layout rules. Complete the import-boundary review before those design tasks.

Key Takeaways

  • Read the actual library item type.
  • Choose the corresponding insertion context.
  • Review replacement and linked-component options.
  • Inspect the resulting structure and any shared locations.

Frequently Asked Questions

Can every library JSON file be imported through the same control?

Use the route intended for the file and item type. The cited Divi 5 guide distinguishes page layouts, sections, rows and modules.

Does importing a layout always preserve the current page?

Review the actual replacement option. The full page workflow can replace existing content, so preserve the destination and verify the selected behavior.

Are imported components always independent copies?

No. The current documentation describes linked components and reuse of matching existing components. Inspect the actual references after the trial import.

Archives