.css file for direct stylesheet use, or as a .json schema for programmatic workflows and external tooling. You choose both the format and the scope of what gets exported each time you download.
Export Formats
.css Stylesheet
A standard CSS file containing all selected global class rules, including responsive
@media blocks. Use this file to import classes into another AtomicKit installation, commit it to version control, or load it as a reference stylesheet..json Design System Schema
A structured JSON representation of your classes, properties, breakpoints, and design token references. Use this format for programmatic processing, design token pipelines, custom tooling, or documentation generators.
.css export looks like this:
.json export follows a schema like this:
Export Scope Options
You control exactly which classes are included in your export using the scope selector.| Scope | What is exported |
|---|---|
| All Classes | Every global class currently registered in Elementor |
| AtomicKit-Tracked Only | Only classes that AtomicKit created or imported — excludes any classes added directly through Elementor |
| Selected Classes | Classes you choose manually using the search-and-filter table |
How to Export
Open the Export Center
In your WordPress admin, go to Elementor → AtomicKit and select the Export tab.
Choose a scope
Select All Classes, AtomicKit-Tracked Only, or Selected Classes. If you choose Selected Classes, use the search table to find and check the classes you want to include.
Common Use Cases
Team sharing and handoff
Team sharing and handoff
Export your design system as
.css and share it with your team. A colleague can import it into their own AtomicKit installation using the Import Center, giving them an identical class set to work with.Staging to production sync
Staging to production sync
Build and refine your design system on a staging site, export it as
.css, then import it on the production site. The diff preview in the Import Center makes it easy to see exactly what will change before you commit.Version control backup
Version control backup
Export your design system regularly and commit the
.css file to your project’s Git repository. This gives you a human-readable history of design system changes alongside your theme code.External tooling integration
External tooling integration
Use the
.json export to feed your design system into style dictionary pipelines, documentation sites, Figma token importers, or any custom tooling that can consume structured JSON.Related
- Import — bring an exported
.cssfile into another AtomicKit installation - Snapshot History — save a restore point before making changes you plan to export