--metadata-name

--metadata-name accepts a semicolon-delimited list of key names and embeds them as <metadata> elements in the primary model file inside the output 3MF archive. It is always paired with --metadata-value, which supplies the corresponding values in the same semicolon-delimited format and must contain exactly the same number of entries. The two lists are read together and parallel-indexed: entry zero of --metadata-name is paired with entry zero of --metadata-value, entry one with entry one, and so on.

At write time the slicer merges the supplied pairs into the same ordered map that already holds every built-in field — including the application identifier, creation and modification dates, model name, designer, origin, description, copyright, license, region, model ID, profile title, profile cover, profile description, designer user ID, designer cover, and the internal 3MF version tag, among others. The custom entries are inserted after the built-in fields are populated. Each value is XML-escaped before being written. The resulting map is then serialized into the <model> root element of 3D/3dmodel.model inside the archive, which is the location the 3MF specification defines for model-level metadata. Any reader that parses that element will see the injected keys alongside the standard ones.

Because the storage is a keyed map, a custom name that duplicates a built-in key will silently overwrite the built-in value in the output. The flag is only active on the 3MF export path; it has no effect on raw G-code or PNG export flows.