Visibility — who can reach it
Public, unlisted, or private. Decides whether the share page is listed in galleries, reachable only by an unguessable link, or not publicly reachable at all.
Loading...
Loading...
Share a whole collection or a single asset. Two independent controls decide the outcome: visibility (who can reach the page) and the privacy preset (what they see once they do).
Every publish dialog asks you two separate questions. They do not constrain each other: an unlisted collection can still expose full provenance, and a public one can expose none. Set both deliberately.
Public, unlisted, or private. Decides whether the share page is listed in galleries, reachable only by an unguessable link, or not publicly reachable at all.
Share, Portfolio, Client, or Archive. Decides how much generation provenance (tool, prompt, seed, model, parameters) appears on the page once someone reaches it.
Listed in galleries and discoverable. Reachable by its clean link and by its hash link. Best for showcasing work you want found.
Never listed anywhere and never resolvable by slug. Reachable only by its unguessable direct link — anyone you send it to can open it, and can forward it. Each video and image in it opens its own page by an equally unguessable link, kept out of search engines. Best for sharing selectively without a login.
Not publicly reachable, even with the correct hash link. This is the base that revocable guest-pass access builds on, which is why no public URL is shown for a private collection.
An unlisted link is unguessable, not secret: whoever holds it can open it and pass it on. When you need to be able to take access back, publish as private and hand out a guest pass instead.
Presets form a gradient. Each one exposes everything the one before it does, plus more. The asset's title is shown at every preset.
No generation provenance at all — no tool, prompt, seed, model, or parameters. The most protective option. Use it for social posts and anywhere the image is the whole message.
Keeps attribution — which tool made it — plus a caption derived from the prompt. The raw prompt text is not rendered. Use it when showcasing work publicly.
Adds the technical generation parameters a client or collaborator needs to judge or re-run the work. Still no workflow graph.
The "glass box" tier: everything Client shows, plus the full prompt rendered on the asset share page. On single-asset shares it also unlocks a sanitised workflow (.json) download for you in the share dialog. Choose it deliberately — it is the least protective preset.
Numonic reads the prompt, model and settings from the file itself where it can (ComfyUI, Midjourney). For anything else — a video rendered from code, an image from an API — it uses the prompt and model the uploader supplied, for example through MCP. Those rows are labelled As stated by the uploader on the share page, and anything read from the file always wins.
The four presets share their names with the export presets, but they answer a different question. Export decides what metadata is written into the file you download; a share page decides what provenance is rendered for a visitor. The Share preset in particular keeps technical metadata in an exported file, but publishes no provenance at all on a share page.
A guest pass is a capability link that grants access to one published collection. It is the only sharing mechanism you can take back after the fact.
Public collections are already reachable without a pass, so the panel appears only once a collection is published as private or unlisted.
The link is displayed a single time when you mint it and is never recoverable afterwards. Copy it before you close the panel; mint a new pass if you lose it.
Choose never, 7 days, or 30 days. An expired pass stops working on its own — you do not have to remember to clean it up.
Every pass is listed with its status — active, expired, or revoked — and can be revoked individually. Revoking one pass does not affect the others.
The pass link opens the gallery directly — recipients never need a Numonic account. The pass is the credential, so treat it like one.
The privacy preset still applies to a guest-pass visitor: a pass changes reachability, never the metadata gradient.
For an agency or studio that needs an outside reviewer to see work in progress without a login, and wants to be able to take access back.
Open the collection, choose Publish, set visibility to Private and pick the Client privacy preset. Private means there is no public URL at all.
In the guest pass panel, choose an expiry (never, 7 days or 30 days) and create the pass. Copy the link straight away: it is shown once and never recoverable.
The reviewer opens it in any browser with no account. Large collections load as they scroll, 50 assets at a time, so a 60+ asset collection opens normally and the rest appear as they continue.
The pass list shows each pass as active, expired or revoked. Revoke one and its link stops working immediately; other passes are not affected.
A guest pass is the credential: anyone who has the link can open the collection until it expires or you revoke it. Do not describe guest passes as password-protected, and send the link only to the people who should see the work. Signed in? The same walkthrough is in Help: Sharing & Publishing.
You do not need a collection to share one image. Open an asset and use Share to publish it on its own page, with its own privacy preset.
Publishing mints a standalone asset page with a copyable link. Assets inside a published collection also each get their own page, linked from the gallery.
The dialog states exactly what each preset will expose before you publish. At the Archive preset you also get a sanitised workflow (.json) download for your own use — API keys, local file paths, and custom-node secrets are stripped out of it.
The dialog reflects the current state, so you can take a single asset down without touching any collection it belongs to.
A collection can carry everything that made a piece, not just the result: the rendered video, the reference images, and the code and data behind it. Code and data files publish as downloads.
Archives (.zip, .tar, .gz), data (JSON, CSV, XML, YAML, text, Markdown) and code (HTML, CSS, JavaScript, TypeScript, Python, notebooks).
These files are served as plain downloads. A visitor’s browser saves them; it never opens or runs an HTML or JavaScript file on a Numonic page.
Code and data files are published exactly as you uploaded them, at every preset. Remove anything you do not want shared before adding the file to the collection.
Add the rendered video, the reference images, and the code or a .zip of the project. Over MCP, upload each with StoreAsset — including the prompt and model in prompt_metadata — and add them with AddToCollection.
Archive shows the full prompt and model on each asset page; Unlisted gives you a link to send without listing the work publicly.
Visitors see the video and images, open each one’s page for its prompt and model, and download the code and data files. No account needed.
A HyperFrames-style title card shared with its references, prompt, model and animation code: the live demo collection.
Published collections and assets each expose a frameable embed URL you can drop into a site, a blog post, or a notebook — the Copy embed control on the share page gives you the URL.
Share links also unfurl into rich previews on platforms that support oEmbed. An embed inherits the privacy preset of the publication it points at, so nothing is exposed through an embed that is not already on the page.
Unpublishing removes the published copies and the share page stops resolving. Links already sent out no longer work.
Publishing again regenerates the published copies at the newly selected preset and visibility. If you published something more openly than you meant to, republishing at a stricter preset is the fix.
Anything a visitor already downloaded stays downloaded. If the audience might change, start private with a guest pass rather than unlisted.
Portfolio piece on social media
Public + Share or Portfolio
Client deliverable, link sent by email
Unlisted + Client
Work-in-progress review with an outside collaborator
Private + guest pass (7 or 30 days) + Client
Reproducible reference for a teammate or a public how-to
Unlisted + Archive
Generation with its references, prompt and code (e.g. a HyperFrames video)
Unlisted + Archive, code in the collection
Decide who can reach your work and how much of the recipe travels with it — separately, every time you publish.