1 · Drop
2 · Review
3 · Pay
4 · Inscribed
Drop a file to inscribe
or click to browse — images, audio, video, documents, HTML, JSON, anything
Review & inscribe
Everything below is pre-set for the best result — expand only what you want to change.
File
Type
Preview — this exact file goes on-chain, test it before you commit
🎵 MP3 with embedded cover art? The SUNO fast-track builds a full on-chain player (Opus + art + lyrics) in one payment.
Options — URI, delivery, margin
Relationships — dependencies & parents (optional)
Dependencies are existence-only links (recursive references). Parents are ownership links:
you send the parent to the deposit wallet with your payment; the child mints linked to it,
then parent + child + change all come back to you.
· Compose a dependency graph →
All-in deposit (over-collected — unused remainder auto-refunded)
—
Cost breakdown
Waiting for a file…
⚡ Fast-track: pay from your connected wallet and the inscription + change return to it automatically.
Batch — one payment, 0 inscriptions, one receipt
Every file below inscribes from a single deposit. Parents (yours, escrowed & returned) can link to every item; deps can reference earlier rows as @0, @1… A single on-chain receipt records the whole batch.
🎵 Audio files detected — how should they go on-chain?
Give each song artwork below: attach an image file (embedded in the player) or enter an image inscription id (recursive artwork — zero extra bytes). Songs with embedded cover art use it automatically.
max 40 items · audio is inscribed as dropped (use the SUNO page to pre-build players)
Shared settings — parents for ALL items, margin, failure policy
All-in deposit for the batch (over-collected — unused remainder auto-refunded)
—
⚡ Fast-track: pay once from your connected wallet — every inscription, the batch receipt, any parents, and all change return to it automatically.
History — all jobs on this browser
| Job | URI | Size | Required | Status | Token |
|---|---|---|---|---|---|
| No jobs yet. | |||||
Advanced — dependency graph composer
Compose a recursive dependency graph
Add nodes for existing inscriptions (by token id) and new files, link dependencies, then send a new node's resolved deps to the wizard.
depends on →
Graph
Layered left→right; arrows point from a node to the inscriptions it depends on.
newexisting