---
title: "Signed URL — Tokenised Video Links Explained | Kinescope"
description: "A signed URL carries a token and an expiry, so a playback link stops working once its window closes. How signing works and what it leaves open."
url: https://kinescope.com/glossary/signed-url
---

# *Signed URL*

A playback link with a cryptographic signature and an expiry time attached. The server checks the signature before serving anything, so a copied link stops working once its window closes — and a tampered one never worked at all.

**Updated:** July 2026 **5 min read** **Security**

In short

A signed URL bakes an expiry and a secret-key signature into a video link, so a copied or altered link is refused before any video is served — but does nothing once a valid stream has begun.

## What is a signed URL?

A signed URL is an ordinary media link with extra parameters appended: an expiry timestamp, optionally a set of constraints, and a signature computed over all of it with a secret key. The edge server recomputes that signature on every request. If it does not match, or the clock has passed the expiry, the request is refused before a single byte of video is sent.

You will also see the same idea called a tokenised URL, a pre-signed URL (the term Amazon S3 uses) or simply link signing. The mechanics are the same: authorisation is carried inside the link rather than in a session on the server. In practice the signature usually covers the [manifest](https://kinescope.com/glossary/manifest) ManifestA small index file (.m3u8 or .mpd) that lists every available rendition and segment so the player knows what it can request.[Open definition →](https://kinescope.com/glossary/manifest) and its segments alike.

Kinescope signs playback links at the CDN level: each link carries an expiry and a signature, and the lifetime is set through the API.

## How signing works

**Your server decides**

A viewer asks to watch. Your backend checks entitlement — subscription, purchase, seat — and only then decides to issue a link.

**The token is computed**

An HMAC is calculated over the path, the expiry and any constraints, using a secret key that never leaves your infrastructure or the platform's.

**The link is handed out**

The token and expiry ride along as query parameters. The link is valid from that moment until it lapses — usually minutes, not days.

**The edge verifies**

Every request to the [CDN](https://kinescope.com/glossary/cdn) CDN (Content Delivery Network)A global network of edge servers that caches video close to viewers, cutting latency and absorbing traffic spikes.[Open definition →](https://kinescope.com/glossary/cdn) is re-checked against the signature. Wrong key, edited path or expired window all return an error instead of video.

Because verification happens at the edge, signing costs nothing in [latency](https://kinescope.com/glossary/latency) LatencyThe delay between a moment happening and a viewer seeing it. Critical for live — Low-Latency HLS brings it down to 2–5 seconds.[Open definition →](https://kinescope.com/glossary/latency) and needs no round trip to your backend during playback. The check is arithmetic, not a database lookup.

## What you can bind a link to

| Constraint | What it means | Trade-off |
| --- | --- | --- |
| Expiry | The link dies at a fixed timestamp | Short windows are safer but break resumed playback if too aggressive |
| IP address | Only the requesting IP may play | Mobile viewers switching between WiFi and cellular get cut off |
| User or session ID | The token carries who it was issued to | Requires your backend to mint links per viewer |
| Path or prefix | The signature covers a specific asset or folder | A per-asset signature is stricter; a prefix is easier to operate |

Expiry plus a per-viewer identifier is the combination most teams settle on. IP binding sounds strongest and causes the most support tickets.

## What signing stops — and what it does not

Signing controls distribution of the link. It says nothing about what happens to the video once playback has legitimately begun.

| Threat | Does signing stop it? | Why |
| --- | --- | --- |
| A link pasted into a group chat | Yes, after expiry | The token lapses; late arrivals get an error |
| Hotlinking your file from another site | Yes | The signature is bound to your parameters, not theirs |
| Scraping predictable file URLs | Yes | There is no valid link without the secret key |
| Downloading during the valid window | No | The bytes are being served legitimately — only [DRM](https://kinescope.com/glossary/drm) DRMEncryption of the video file plus a licence server that issues a per-session key — so a downloaded copy stays unplayable.[Open definition →](https://kinescope.com/glossary/drm) makes them unusable afterwards |
| Recording the screen | No | Nothing in the link layer touches playback |

That last pair is the reason signed links and DRM are not alternatives. Signing decides who may start a stream; DRM decides whether the delivered file is worth anything once it lands.

## Signed URLs versus the other controls

**Password or login**

Guards the page. Once the player is loaded, the [HLS](https://kinescope.com/glossary/hls) HLS (HTTP Live Streaming)Apple’s adaptive streaming protocol. Uses .m3u8 manifests and segmented delivery; supported on every browser, device and smart TV.[Open definition →](https://kinescope.com/glossary/hls) media URL is visible in developer tools and works for anyone who copies it — unless it is signed.

**Domain restriction**

Stops your embed playing on other sites, but does nothing about a direct link to the file itself.

**Signed URL**

Makes the direct link temporary and non-transferable. The gap it leaves is what happens during the valid window.

**DRM**

Encrypts the payload so a download taken inside that window is still unplayable. The layer below the link.

How Kinescope handles this

### Kinescope signs and verifies every playback link at its own edge

Kinescope signs playback links for you: expiry and per-viewer binding are configured per project, verified at our own [CDN](https://kinescope.com/products/content-delivery-network) edge, and combine with [DRM](https://kinescope.com/glossary/drm) DRMEncryption of the video file plus a licence server that issues a per-session key — so a downloaded copy stays unplayable.[Open definition →](https://kinescope.com/glossary/drm) and domain rules rather than replacing them. Your backend keeps the entitlement decision — see [video access control](https://kinescope.com/solutions/video-hosting-drm) for how the layers stack, or [secure video hosting](https://kinescope.com/products/video-hosting) for what comes with it.

[See secure video hosting](https://kinescope.com/solutions/private-video-hosting)

## Further reading

-   [HMAC — Wikipedia](https://en.wikipedia.org/wiki/HMAC) — the signing primitive behind most token schemes.
-   [DRM](https://kinescope.com/glossary/drm) — the layer that protects the payload rather than the link.
-   [Secure video hosting: what it means and how to choose](https://kinescope.com/blog/secure-video-hosting-guide).
-   [Anti-piracy for video](https://kinescope.com/solutions/anti-piracy-video) — how signing, DRM and watermarking stack.

[![Denis Konnov](https://kinescope.com/blog-assets/authors/denis-konnov.jpeg)](https://kinescope.com/authors/denis-konnov)

Written by

[Denis Konnov](https://kinescope.com/authors/denis-konnov) Verified

CMO at Kinescope

Denis leads marketing and content at Kinescope, working closely with the platform's engineers. This glossary is reviewed and kept up to date by the team building Kinescope's streaming, encoding and CDN delivery infrastructure.

## FAQ

Can’t find the answer you need? Check out our [Help Center](https://docs.kinescope.com/).

A media link carrying an expiry timestamp and a cryptographic signature. The server recomputes the signature on each request and refuses anything expired or altered, so the link works only for its intended window.

Minutes rather than hours for the manifest, with the player refreshing as needed. Long windows are convenient and are exactly what gets pasted into group chats; very short ones break resumed playback and long pauses. Most teams land between five minutes and an hour.

No. While the link is valid the bytes are served normally, so anything that can play the stream can also save it. Signing controls access to the link; DRM controls whether a saved copy is usable.

They solve different halves. Signed links stop hotlinking, scraping and sharing after expiry; DRM makes a captured file unplayable. For paid content the sensible answer is both, with signing as the cheap outer layer.

## Links that expire, keys that do not leak.

Kinescope signs and verifies playback links at its own CDN edge, alongside DRM and domain rules.

[Start free](https://app.kinescope.io/user/create?lang=en)[Read the docs](https://docs.kinescope.com/)
