Hotlinking and Embedding Assets

• Getting the right URL
• Where hot-linking is the wrong choice
• Embedding responsibly
• Official source
• Related reading

Hot-linking is explicitly supported. The Vault is a public read-only repository, and its files may be referenced directly from your own HTML, CSS, Markdown or JSX — no account, no key, no rate limit. That is a deliberate policy rather than an oversight, and it changes how you should build: for web use, pointing at the canonical URL is better practice than copying the file into your own project, because you stay current automatically.

Getting the right URL#

Take it from the asset's own detail page in the Vault. URLs copied out of a rendered page elsewhere — a showcase, an article, a social preview — may point at a resized derivative or a presentation-layer path that is not intended as a stable reference.

Where hot-linking is the wrong choice#

Three cases. Print, where you need a fixed file at a fixed resolution. Offline or packaged work, which cannot fetch anything. And anything that must not change under you — a comparison, an archived snapshot, a legal exhibit. In those cases download, and record which version you took.

Embedding responsibly#

Respect what the file is: do not stretch a logo, do not re-encode a video into something worse and present it as official, and do not composite official assets into a mark of your own. The terms on the asset page govern; this is guidance about practice, not a licence.

Official source#

Canonical source for this subject: the Xdripian Asset Vault. Checked 21 August 2026 — where this guide and the live service disagree, the service is right.

Related reading#

• Attribution, Licensing and Terms — Where the terms for a file actually live and how to credit the project correctly.
• File Integrity, Naming and Versioning — Keeping track of which version of an asset you actually used.
• Linking Multimedia, Library, Codex and Assets — Choosing between the four surfaces that can each hold a piece of the same work.