Repository navigation
edit ungroup
< Previous: Group | Next: Copy >
Ungroup (command)Dissolve the selected group(s), freeing their members.
Menu: Edit > Ungroup | In depth: The Layers panel
Ungroup dissolves the folder and hands its members back, each selectable on its own again. The objects are untouched; only the folder goes.
The freed members come back selected, so whatever you wanted them individually for is one gesture away.
Not always the top level, which is the part the old description got wrong. If the group you dissolved was itself inside another group, its members land in that parent, at the slot the dissolved group occupied. Ungrouping one layer of nesting does not throw its contents out to the root of the tree.
That is what you want almost always: a folder inside a folder is usually organizing, and dissolving the inner one should leave the outer one intact.
A group made by the node graph, the folder a Realize node fills with its output, is managed, and Ungroup does nothing to it. Not a refusal, not an error, simply nothing.
The reason is that the group is not really a folder there, it is the node's own record of what it built. Dissolving it would leave objects whose owner no longer knows it owns them.
When you want those objects loose and hand-editable, Bake is the command for it: it turns the node output into free geometry and hides the node-owned copy, which is the honest version of what ungrouping a managed group would be trying to do.
Worth saying on this page because ungrouping is when people discover it. A group is a folder in the Layers panel, not a construction relationship. Nothing in a group depends on the group, and nothing depends on a group for its position or its size.
So ungrouping cannot break a construction. Whatever was built on the members is still built on the members, and it does not notice that the folder around them is gone.