Inscription sandbox · proves an artifact renders under ord's content CSP before you spend a single sat ·
← back to studio
1 · Source Artifact
— or paste / drop an artifact .html below
drop an artifact .html file here
2 · Recursive Resources optional
Map a font (or any file) to a fake inscription id so the artifact's
url(/content/<id>) reference resolves during the test.
2b · Living Episodes optional · living parents only
Attach raw episode payloads (.bin from the studio's Episode mode) as
children of the loaded artifact. The sandbox serves ord's real /r/children shapes, so a living parent
discovers and appends them exactly as it would on-chain. Attach → Reload Frames → watch the frame count grow.
frames decoded: —
3 · Result
Awaiting artifact…
Artifact size
—
Loads in iframe
—
Canvas present & sized
—
Frames actually paint
—
Runtime JS errors
—
CSP violations (strict origin)
—
How to read this: the strict frame (sandbox=allow-scripts) runs your artifact in an
opaque origin — the harshest case ord may use, where same-origin recursive fetches are blocked. The
same-origin frame (allow-scripts allow-same-origin) lets the harness auto-click play and read the
canvas to confirm frames paint. CSP violations are captured server-side, so they're detected even in the
strict frame the page can't read into. A clean strict frame is the safe bet for mainnet.