Oombla DocsMenuoombla.com

Basic Operation

How to set up asset nodes for export

There are two main prerequisites for getting a collection of assets ready for Export Code:

  1. They must all be in the same frame (or component or instance), and
  2. the individual assets must all be direct children of the selected frame.

Below are some visual examples.

Correct! Icons direct children of the same frame

All of the assets to be exported are direct children of the same frame.

Screenshot of Figma user interface showing assets as direct children of the same frame.

Screenshot of Export Code plugin showing all assets ready for download.

The selected node must be either a Frame, Component or Instance (copy of a Component). For the selection, the plugin will export any of the following node types if they are direct children of the selected node:

  • BooleanOperationNode
  • ComponentNode
  • EllipseNode
  • FrameNode
  • InstanceNode
  • LineNode
  • PolygonNode
  • RectangleNode
  • SliceNode
  • StarNode
  • VectorNode

The rest will be ignored (note how the text label is ignored in the example above). You can read more about node types in the Figma Plugin API documentation.

Wrong! Icons in sub-groups

If icons are in subcategorized into groups within the selected node, they will be ignored. Note how the icons in the “Row 2” group are ignored in the export.

Screenshot of Figma user interface showing the second row of icons collected into a subgroup.

Screenshot of Export Code plugin with the icons in the subgroup missing from the assets ready for download.

Wrong! Icons not grouped

If the icons are not collected into a single Frame, Component or Instance there will be no option to export them all at once. However, you can export any of the assets individually if that were a desire.

Screenshot of Figma user interface with all of the assets at the top level of the layer hierarchy.

Screenshot of Export Code plugin’s select box with no option to export all assets at once.