Sharing Nodes

A .surfacenode file packages one node, or one subgraph, so it can be handed to another person or another project. It is a small ZIP; see Project & File Formats for the format details.

Exporting

Choose Export .surfacenode… from the node’s context menu. The entry appears only when exactly one library or subgraph node is selected. It writes a self-contained package through a save dialog; canceling the dialog does nothing silently.

Success reads “Exported <node name> as .surfacenode”; failure reads “Export failed - no file was written”.

missing screenshot

A node’s context menu with the Export .surfacenode… entry highlighted.

What is in the package

Entry	Contents
node.xml	The node’s type, label, all parameter values, seed, resolution mode and override, bit-depth mode and override, and its ports including values set directly on unconnected inputs
thumbnail.png	The node’s last rendered output, written only when the node has already been evaluated

Connections are not part of the package: it describes one node in isolation. A missing thumbnail is not an error; previews regenerate.

Embedded media and tags are not bundled

Imported bitmaps are not packaged into a .surfacenode. A node that depends on an imported bitmap will not carry that bitmap with it. Neither do node tags travel: they are part of your own library vocabulary, kept in Settings → Library, not part of the node. Project tags are the exception - those are written into the .surfacelabs archive and do travel with a project you share.

Importing

Use the Import .surfacenode… button at the bottom of the Node Library panel. The imported node is placed at the viewport center with a fresh identity.

missing screenshot

The Node Library panel with the Import .surfacenode… button at the bottom.

If the import goes wrong:

• A package referencing an unknown node type reports Unknown node type "…" - cannot place.
• A corrupt file reports Could not import .surfacenode - file is invalid.
• Non-fatal issues surface as individual warning toasts.