Skip to content
Tracking cookies 0 % Revenue share 4K 4K & HDR ISO 27001 German servers only No cookie banner No US cloud 100 % 100% Ad-free

01 Reference

Options, sizes and troubleshooting.

Everything you need to know about the AboveStream embed: which parameters the player understands, when to use which code, what helps with a 403, and what can be said about privacy.

02 Options

Playback options

The player at /embed/{token} reads four optional parameters from the address. The embed generator in the dashboard writes them into the link and the code for you.

Playback options
Parameter Values Effect Default
t whole seconds, 1 to 86400 The player jumps to this position on load. start of the video
autoplay 1 or 0 1 starts automatically and muted. 0 prevents autostart, even if your workspace player setting enables autoplay. not set: the embed tries to start as before
muted 1 or 0 Starts without sound. 0
loop 1 or 0 Repeats the video endlessly. 0
Example address
https://videos.abovestream.de/embed/TOKEN?t=90&autoplay=1&muted=1&loop=1

On plans with signed embeds (Pro and up) the generator's link also carries a sig parameter. Do not change it.

Good to know

  • Invalid values never cause an error An invalid value falls back to the default. For t, 0, negative numbers, values above 86400 and text count as invalid. Unknown parameters are ignored.
  • Autoplay always starts muted Browsers only allow automatic playback without sound. The player therefore mutes with autoplay=1 or muted=1. This applies to that one load only and does not change the viewer's saved volume.
  • The generator does not start on its own It writes autoplay=0 into the address explicitly. Nobody expects a video pasted into an article to start by itself. If you switch autoplay on, it also sets muted=1.
  • No end card with a loop With loop=1 the video jumps back to the beginning, not to the start time. Because the video never ends, the end card and the hint for the next episode do not appear in this embed.

03 Size

Responsive or fixed size

The default is responsive. You only need the fixed size if your system cannot handle the responsive code.

Responsive (default)

A wrapping div keeps the video's aspect ratio and the iframe fills it. The player adapts to any column width. The aspect ratio comes from the video, with 16:9 as the fallback.

Responsive (default)
<div style="position:relative;width:100%;aspect-ratio:1.7778;">
  <iframe
    src="https://videos.abovestream.de/embed/TOKEN?t=90&amp;autoplay=0"
    title="Video title"
    style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;"
    loading="lazy"
    allow="autoplay; fullscreen; picture-in-picture"
    allowfullscreen
    referrerpolicy="strict-origin-when-cross-origin"></iframe>
</div>

Fixed size

A single iframe with width and height in pixels. The generator works out the height from the video's aspect ratio. Widths from 160 to 3840 pixels are allowed.

Fixed size
<iframe
  src="https://videos.abovestream.de/embed/TOKEN?t=90&amp;autoplay=0"
  width="800"
  height="450"
  title="Video title"
  frameborder="0"
  style="border:0;"
  loading="lazy"
  allow="autoplay; fullscreen; picture-in-picture"
  allowfullscreen
  referrerpolicy="strict-origin-when-cross-origin"></iframe>

The responsive snippet uses inline styles. If your system strips them (common on editorial and learning platforms), use the fixed size. Line breaks in the code change nothing; the generator delivers it on one line.

04 Domain restriction

Protection against other sites

From Pro you can set the domains an embed plays on. To do that the player checks which page it is loaded from.

  • The referer decides The host of the referer your browser sends is compared. An entry example.com also allows www.example.com, but not evilexample.com. An entry with a subdomain does not allow the main domain. Enter the host name only, without https:// and without a path.
  • Without a referer you get 403 If the referer is missing or comes from a domain that is not allowed, the embed answers with 403. That is why a restricted embed cannot simply be opened directly in the browser. The iframe code sets a referrer policy that sends at least the origin of your page.
  • Only the iframe code is reliable Many editors fetch a pasted link in the background, without a referer. Restricted embeds turn them away. The generator therefore shows only the iframe code.
  • It is hotlink protection, not access control The check relies on the referer a browser sends. It stops other sites from embedding your video. A custom client can set the header itself. For confidential content you need more than this restriction.

05 Troubleshooting

When the player does not appear

The most common causes, in order of likelihood.

The player shows a 403 error

The embed has a domain restriction, and the page that loads the player is not on the list, or no referer arrives. Open your browser's developer tools and look at the referer of the request to /embed/… in the network tab. Its host belongs on the list. With site builders that can be the tool's domain. If your page sets the referrer policy no-referrer, the browser sends no referer; leave the code's referrerpolicy attribute unchanged.

The browser blocks the iframe (Content Security Policy)

If your page sets a Content Security Policy with frame-src, the player's address has to be listed there. If frame-src is missing, MDN says child-src applies, and if that is missing too, default-src. Add the host from the src of your code. You set this in the server configuration or in the tool you run your page with.

The page loads but the iframe stays empty (HTTP instead of HTTPS)

An HTTP iframe on an HTTPS page is mixed content, and browsers block it. The AboveStream code uses HTTPS; do not change the address to HTTP. According to their help, some site builders only display HTTPS code anyway.

The video does not start automatically (Safari, phone)

Browsers generally allow autoplay only without sound, which is why autoplay=1 always starts muted. In addition the iframe has to allow autoplay: the allow attribute in the code contains autoplay, and some systems remove it. Browsers may also block autoplay depending on settings and device. That is browser behavior, not a defect of the embed. Do not expect every video to start by itself on a phone.

WordPress shows no fullscreen button

If you only paste the link, WordPress builds the player itself and filters the HTML for providers it does not know: only a few iframe attributes remain, and the iframe runs with sandbox="allow-scripts". Without allowfullscreen it cannot request fullscreen, and inside a sandbox the player generally cannot save settings such as volume. Use the iframe code in the "Custom HTML" block.

The video appears with no height or distorted

Your system has probably stripped the inline styles of the responsive code. Generate the fixed-size code in the generator. For Wix and Webflow the vendors also recommend giving sizes in percent rather than pixels.

My pasted link does not turn into a player

The link is only converted if the editor supports oEmbed discovery and the embed has no domain restriction. Many editors do not. Use the iframe code in that case.

The link preview in Slack or Discord shows no image

A preview image and title exist only for share links without a password and without a domain restriction. Videos under a country rule have no preview image. How long a service caches a preview is up to the service.

06 Privacy

Embedding and privacy

What we can say about the player, and where your own assessment begins.

  • No tracking cookies AboveStream embeds set no tracking cookies and do not transfer playback data to third countries. Core processing stays in German data centers. A consent banner is therefore not required for plain video playback.
  • DPA available A data processing agreement (DPA) is available. View the DPA
  • The rest of your page counts separately These statements apply to the AboveStream player. Analytics, fonts, maps and other services on the same page are assessed separately.
  • Services in between If you embed through a tool that loads content itself, its privacy notices apply too. Notion, for example, states in its help that Iframely and the embedded app may receive the IP address of viewers. This is not legal advice.

07 Sources

Where the browser information comes from

The statements on autoplay, Content Security Policy, mixed content and referrer policy rest on the following pages, retrieved on November 11, 2026.

08 Read on

Next

09

Copy the code, paste it, done.

Included in the free plan. Upload a video, choose the options, paste.