Icon packs

Move icon collections between sites as one ZIP: export any collection, import it elsewhere, or commit it to your repository. Includes the manifest format.

An icon pack is a collection packed into one ZIP file. You use it to take icons from one site to another, to hand a client's icons to a colleague, or to keep icons in your theme's Git repository. This guide shows how to export, how to import and what is inside a pack.

Before you start

Your Pro license is active.
To import a pack as an editable set: Icon set editor is on under Icons → Features.
To use a pack as a folder: Theme & folder sources is on.

What is inside a pack?

A pack is a ZIP with two kinds of files, side by side:

manifest.json, a small text file that names the collection and lists its icons with labels. "Manifest" simply means a list of contents.
The SVG files, one per icon.

house-icons.zip
├── manifest.json
├── front-door.svg
└── window.svg

The same ZIP works two ways:

Way	How	Result
Upload	Icons → Packs → Import a pack	An icon set you can edit in WordPress
Unzip into a folder	Unzip to `wp-content/easy-svg-icons/house-icons/`	A read-only collection that lives in your files, for example in Git

Export a collection

Open Packs

Go to Icons → Packs and scroll to Export a collection. Every collection is listed, whatever made it: a set, a folder, the theme or the free icon library. Under each one you see where it comes from, for example "Icon set, made on this site" or "Theme Twenty Twenty-Five".

Download one

Click Download next to the collection. You get slug.zip.

Or download several

Tick up to 25 collections and click Download as one zip.

You can also export only some icons: in Icons → Icon library, click Select several, tick up to 100 icons and click Export.

Import a pack on another site

Open Packs

On the other site, go to Icons → Packs.

Choose the ZIP

Under Import a pack, click Choose a pack… or drop the ZIP.

Handle a taken name

If a collection with that name already exists, you see "A collection of that name already exists. Import it as ... instead?" Click Import under that name to accept the free name.

The icons are cleaned like any upload and stored as a new set. Nothing from the ZIP is written to your server's files.

When a name is already taken

Door	What happens
Upload	You are offered a free name and decide.
Folder	Nobody can be asked, so the folder moves aside on its own: it takes the `slug` from its `manifest.json` if that is free, otherwise the folder's name, otherwise that name with a number.

The folder's name is worked out again on every page load. If the collection it moved aside for disappears, the folder gets its preferred name back.

Keywords survive in a folder but not in an upload. A set stores only each icon's name and label.

The manifest

{
  "version": 1,
  "slug": "house-icons",
  "label": "House icons",
  "icons": {
    "front-door": {
      "file": "front-door.svg",
      "label": "Front door",
      "keywords": ["entrance", "door"]
    }
  },
  "license": "CC0-1.0",
  "author": "Your agency",
  "source": "https://example.com/packs/house-icons"
}

Field	Required?	Meaning
`version`	Yes	The manifest format. Leave it at `1`. A pack with a newer number than your plugin knows is refused as a whole.
`slug`	Recommended	The collection's address, for example `house-icons`. Icons are then called `house-icons/front-door`.
`label`	Recommended	The collection's name people see.
`icons`	Yes, not empty	One entry per icon. Each may give `file`, `name`, `label` and `keywords`. Without `file`, the file named after the entry is used: `"alpha"` means `alpha.svg`.
`license`, `author`, `source`	No	Free text. Shown under the collection on the Packs screen, never acted on. `source` is never opened.

A manifest describes the folder, it does not limit it. An SVG without an entry still imports, named after its file.

Good to know

The license fields matter. Comments inside SVG files are removed by the sanitizer, so a credit written inside the files does not survive. Put it in license, author and source.
Problems are listed. Under each folder collection the Packs screen lists files that could not be used, with the reason, for example "the file is above the size limit" or "it is not a safe SVG".
WP-CLI. Developers can do the same on the command line with wp easy-svg pack list, export and import.

Common questions

Import icons

ZIPs, fonts, Font Awesome and presets.

Icon Pack Starter

Ship a pack as its own plugin.

Developers: the full format is in The manifest, the commands in WP-CLI.

Was this page helpful?