
To embed an AIOZ Stream livestream on your website, open the live session, click Share and paste the iframe code into your page's HTML. To share it without embedding, copy the Public Playback URL from the Settings panel and send it as a link, and both options come from the same session.
TL;DR:
Sharing a link is the faster option, because you only paste the Public Playback URL into a chat or an email and viewers watch wherever it takes them. Embedding takes a few more minutes of work, but your viewers stay on your page while they watch.
The embedvid guide to live stream embedding puts the link side plainly: it "sends visitors away from your website to watch the stream somewhere else." An iframe, by contrast, "tells your web page to open a rectangle and show content from another website inside it."
| Public link | Embedded iframe | |
|---|---|---|
| What you copy | Public Playback URL from the Settings panel | iframe code from the Share button |
| Where viewers watch | At the playback URL | Inside your own page |
| Pick it when | You need to share fast in chat, email or a social post | You want the stream beside your own content, branding or call to action |
One session can serve both at the same time.
Both options start from a running session, so connect your encoder first. If you haven't created one, the go-live guide and the article on stream keys versus streaming sessions cover that part.
<iframe ...></iframe> code into your page's HTML.The Settings panel also lists the editable title, the resolutions available to viewers and the archive status, so you can confirm each of them before you share anything.

If you want to build your own page, the streaming session object carries the same information. Its assets block lists thumbnail_url, hls_url, iframe and player_url. A GET request lists your sessions, authenticated with the stream-public-key and stream-secret-key headers as the API keys guide explains.
curl "https://api.aiozstream.network/api/live_streams/KEY_ID/streamings" \
-H "stream-public-key: YOUR_PUBLIC_KEY" \
-H "stream-secret-key: YOUR_SECRET_KEY"This excerpt keeps the fields that matter here from the object the docs show for each session, and its values are the docs' placeholders, not real output.
{
"id": "streaming_id",
"key_id": "key_id",
"title": "streaming_title",
"assets": {
"thumbnail_url": "thumbnail_url",
"hls_url": "hls_url",
"iframe": "iframe",
"player_url": "player_url"
},
"save": true,
"status": "created"
}The docs do not say which of player_url and hls_url matches the Public Playback URL, or what the iframe field contains. Compare each field against the dashboard values of a test session before you build anything on one of them.
The player documentation prints one iframe pattern, and it is for video on demand, as the vod/hls/video_id path in the source shows.
<iframe
src="https://embed.aiozstream.network/vod/hls/video_id"
width="100%"
frameborder="0"
scrolling="no"
allowfullscreen="true"
></iframe>The livestream docs only say to paste <iframe ...></iframe> from the Share button. They show no live path, so don't swap vod for live and hope that it works. Copy the code the dashboard gives you instead, because that is the only version the docs vouch for.
Two page-level touches use standard HTML and CSS that don't depend on AIOZ. First, wrap the pasted iframe in a container with aspect-ratio: 16 / 9, which MDN describes as a way to define the desired width-to-height ratio of an element's box. The VOD embed guide shows a full responsive example with the same wrapper pattern, which you can adapt to the code that Share gives you. Second, add loading="lazy" to the iframe if the stream sits below the fold, since MDN says it defers loading until the frame nears the viewport.
Anyone who has the link can watch. The sharing page states that "The Public Playback URL is publicly accessible to anyone with the link unless access control is enabled." The live pages never explain how to turn access control on or what viewers see when it is active, so treat every livestream URL as public for now.
Keep the two secrets apart, because the playback URL lets people watch while the stream key lets people broadcast. The create-livestream docs warn that "Anyone with this key can broadcast to your channel," so close the Settings panel before you screen-share or record, since it shows the key.
For video on demand, the docs list an is_public flag and a playback token, which the DRM article covers. Test whether either one applies to live sessions before you rely on it.
The docs answer only part of this question: past livestreams are only available for replay if Save Stream to Archive When Finished was enabled. The Settings panel shows the saving status, so check it before you go live, and the complete guide to live streaming explains how archived sessions become media.
What an embedded player shows before your encoder connects, during a dropout or after you stop isn't documented. Other services differ: embedvid says its embeds fall back "gracefully when you're offline, showing your recent videos or a custom placeholder instead of an error." Put the start time in text on your page, so early arrivals know what to expect.
A short rehearsal fills in some of what the docs leave open. Follow these steps with a throwaway session title and a staging page, not your live page.
How do I embed an AIOZ Stream livestream on my website?
Open the active streaming session, click Share and paste the iframe code into your page's HTML. Do not build the URL yourself or copy it from the video-on-demand docs.
Where is the Public Playback URL?
Click the Settings icon in the player view, and you will find it in the Settings panel as a read-only field that you can copy.
Is an AIOZ Stream livestream link private?
No, because the docs say the Public Playback URL is publicly accessible to anyone with the link unless access control is enabled. They don't describe how to enable it for live sessions.
Can viewers replay an embedded livestream after it ends?
Only if Save Stream to Archive When Finished was enabled for that session. The docs don't say whether the original embed code plays the replay, so test it first.
Can I use the video-on-demand iframe URL for a livestream?
No, because the documented URL pattern is for video on demand and has vod in its path, so copy the livestream code from the Share button instead.

Video streaming protocols move video from encoder to viewer. See how RTMP, SRT, HLS, DASH and WebRTC differ in latency, transport and where each one fits.

Decentralized live streaming sends a real-time broadcast through independently run nodes instead of one company's servers. Here's how each stage of it works.

A video streaming glossary of 114 terms, from AAC and ABR to WebRTC and Widevine, each defined in plain English with sources and links to the deep posts.

Read the AIOZ Stream Statistics panel: bitrate in and out, FPS in and out and current viewers, plus the documented rules for each and what the docs leave out.

Embed an AIOZ Stream livestream with the Share button's iframe or send the Public Playback URL as a link. Covers API fields, public access limits and doc gaps.

Learn how a stream key differs from a streaming session on AIOZ Stream, what each one stores, and what to preconfigure before you go live. Docs-based guide.