Skip to content

SteadyLink documentation

Host files behind links that never change. Upload once, replace the file whenever you need to, and every place that uses the link gets the new version.

On this page

SteadyLink gives every file one permanent address. When you publish a new version, the address stays the same and starts serving the new bytes. Websites, emails, QR codes, apps, and printed material keep working without anyone editing a link.

Stable linkcdn.steadylink.io/a/3f2a…Pinned link/a/3f2a…?v=2currentRevision 1hero.webp, Mar 2Revision 2hero.webp, Apr 18Revision 3hero.webp, today
The stable link follows the current revision. A ?v= link stays on one revision.

Start here#

Pick the tool that fits where your code runs. They all use the same API and the same scoped workspace keys.

The model in one minute#

  • A workspace holds your buckets, members, API keys, usage, and settings.
  • A bucket is a top-level container with its own defaults. Folders are paths inside it.
  • A file (also called an asset) has one stable identity and one stable link: https://cdn.steadylink.io/a/{asset_id}.
  • Each upload to that file creates a new revision. The link serves whichever clean revision is current, and you can roll back at any time.
  • Every upload is scanned for malware. A file that fails the scan is blocked from delivery.
  • Files are public or private. Private files are shared with expiring, revocable signed links.

Read Concepts for the details behind each of these.

Get help#

If something in these docs is wrong or missing, email [email protected] with the page URL. For API failures, include the X-Request-Id from the response so we can find the request in our logs. Current platform health is on the status page.