How to Start a Livestream on AIOZ Stream: OBS and Mobile Setup

TL;DR:

• Going live on AIOZ Stream takes seven steps: create a stream key, start a new stream under it, fill in the session form, create the stream, paste the server URL and key into your encoder, start broadcasting, then share the playback URL.
• Only two things must exist before your encoder connects: a stream key and valid credentials. The PRISM mobile guide says AIOZ Stream can create the session automatically once you start streaming.
• Decide on archiving before you go live. Past livestreams are only replayable if "Save Stream to Archive When Finished" was enabled during the broadcast.
• Check your upload speed first. The docs recommend 4500 to 6000 Kbps video in OBS, which means a connection with roughly 7 to 9 Mbps of consistent upload once you add audio and a safety margin.
• In the first two minutes, watch the statistics panel (current viewers, bitrate, FPS) and compare the incoming bitrate with what you configured.

Before you start: a five-minute pre-flight

Most failed first broadcasts come from the environment, not the platform. Four checks catch nearly all of them.

Pick your encoder. AIOZ Stream documents two: OBS Studio on desktop, suited to scenes, overlays and external cameras, and PRISM Live Studio on mobile, suited to on-the-go streaming. Both connect over RTMP with a server URL and a stream key.

Measure your upload speed, not your download speed. Run a speed test at least three times, at the time of day you normally stream, on the network you will broadcast from, and note the lowest consistent number. Switcher Studio's bandwidth guide recommends using no more than 60 to 70 percent of your consistent upload speed, and offers multipliers on your total stream bitrate: 1.3 for a stable wired connection, 1.4 for most home and small-business connections, and 1.5 for WiFi, shared networks or venues.

Apply that to the documented settings. The OBS guide recommends 4500 to 6000 Kbps of video plus 128 to 160 Kbps of AAC audio, so the total stream is about 4.6 to 6.2 Mbps. At the 1.4 multiplier you want roughly 6.5 to 8.6 Mbps of consistent upload; at 1.5 (WiFi, a venue), roughly 6.9 to 9.2 Mbps. On mobile, the PRISM guide recommends 4000 Kbps for 1080p on Wi-Fi and 2500 Kbps for 720p on 4G or 5G, which at 1.4 means about 5.6 Mbps and 3.5 Mbps respectively, before audio. If your measured upload falls short, lower the resolution and bitrate rather than hoping the stream holds.

Prepare the device. The PRISM guide lists stable internet, enough upload bandwidth, camera and microphone permissions, and adequate battery. These sound obvious until they are the reason a stream drops mid-broadcast.

Decide where the key will live. The stream key is a secret credential. The docs repeat the same rule in every setup guide: keep it private and never show it in screenshots or recordings. If it is ever exposed, regenerate it before going live again.

The seven steps

1. Create a stream key. In the AIOZ Stream Dashboard, open the Live Streaming tab and choose "Create Stream Key". Give it a name such as "Main Channel" and pick the type: "Video" for OBS or PRISM broadcasts, or "Audio" for audio-only workflows. Save it.
2. Start a new stream. In the Live Streaming list, select the row for your key and choose "Start new stream".
3. Fill in the session form. A title is required. Optional fields are the desired output resolutions (the docs give 720p and 1080p as examples), a JPG or PNG thumbnail, restream destinations, and the archive checkbox, "Save Stream to Archive When Finished".
4. Create the stream. The Create Stream button only becomes active once all required fields are complete, so a greyed-out button means the title is missing.
5. Copy your credentials into the encoder. You need two values from the dashboard: the Server URL (the RTMP URL) and the stream key. In OBS, open Settings, then Stream, and set the service to Custom, as the OBS overview guide describes for a custom streaming server, then paste the server URL and the key. In PRISM, choose Custom RTMP, enter a stream name, and paste the same two values.
6. Start broadcasting. Press Start Streaming in OBS or go live in PRISM. Use the documented starting settings: for OBS at 1080p30, CBR rate control, a 1 second keyframe interval and the High profile; for PRISM, 30 fps with a 1 second keyframe interval.
7. Share the broadcast. Copy the Public Playback URL, or use the Share button to copy the embed code, an iframe you can place on your own site.

The shortcut: going live from your phone without a session

The mobile guide contains a detail the dashboard steps do not make obvious: you do not need to create a livestream in the dashboard before going live. AIOZ Stream can create it automatically after you start streaming with valid credentials. In practice that means the key is the only setup step you cannot skip, which makes spontaneous mobile broadcasts quick. The trade-off is that you skip the session form, so the title, resolutions, thumbnail, restream destinations and archive option are the things you would otherwise have set there. If replay matters, create the session in the dashboard first.

Three decisions to make before you press go

Archiving. The viewing guide is explicit: past livestreams are only available for replay if the archive option was enabled during the broadcast. If you might want the recording, tick the box in the session form. The update endpoint of the API also accepts a save field, but the documentation does not say whether it can be changed on a broadcast that is already running, so do not rely on fixing it afterward.

Resolutions. The session form lets you choose output qualities. Choose only what your source and your viewers justify; there is no benefit in offering 1080p if your upload only sustains 720p.

Restreaming. If you want the broadcast to appear on other platforms, add destination RTMP URLs in the session form, or through the multicast API. Because destinations are configured on the AIOZ Stream side rather than inside OBS, the documented setup has your encoder sending a single stream. The docs do not describe how the forwarding works or how many destinations are allowed, so test your target count before an important event.

The first two minutes after going live

Open the player and look at the statistics panel. It shows "Current Viewers" plus bitrate and FPS for diagnosing the connection. Through the API, the same family of numbers is available from the statistics endpoint as fps_in, fps_out, bitrate_in, bitrate_out and data_transferred, refreshed every 5 to 30 seconds. The "in" values are what your studio uploads; the "out" values are what viewers receive.

Compare bitrate_in with what you set. If it sits well below your target, your connection or encoder is the constraint, and lowering the bitrate is the fix. If FPS is low, the machine is struggling to encode. When viewers report buffering, Stream Health Metrics Explained covers how to read the symptoms.

If something looks wrong

• The Create Stream button is disabled: a required field is empty. The title is the required one.
• The encoder will not connect: re-copy the server URL and key with no extra spaces, and confirm the key is the one for the right stream. The docs describe "valid credentials" as the condition for a stream to start.
• You shared the key by accident: regenerate it before going live again, as both guides instruct.
• No recording afterwards: the archive option was off for that session.

The documentation does not include a troubleshooting table of error messages, so a short dry run with a throwaway title is the most reliable way to learn how your setup behaves before a real event.

FAQ

How do I start a livestream on AIOZ Stream?
Create a stream key in the dashboard's Live Streaming tab, start a new stream under it, then copy the server URL and key into OBS or PRISM and start broadcasting.

Do I need to create a session before I stream?
Not necessarily. The PRISM guide states that AIOZ Stream can create the livestream automatically after you start streaming with valid credentials. Create the session yourself when you want to set the title, resolutions, thumbnail, destinations or archiving up front.

Can I stream from my phone?
Yes. The documented mobile path is PRISM Live Studio with a Custom RTMP service, using the same server URL and stream key as desktop.

Can I stream audio only?
The stream key has a type: "Video" for OBS and PRISM broadcasts, and "Audio" for audio-only workflows.

How much upload speed do I need?
Take your total stream bitrate (video plus audio) and multiply it by 1.3 to 1.5, depending on how stable your connection is. For the documented 1080p30 OBS settings, that is roughly 6.5 to 9.2 Mbps of consistent upload.

Will my broadcast be saved?
Only if "Save Stream to Archive When Finished" was enabled during the broadcast. Otherwise past livestreams are not available for replay.

Related Reading

• Stream Key vs Streaming Session: Preconfiguring a Livestream: the difference between the key you create and the session you configure
• OBS Studio Setup Guide for AIOZ Stream (the OBS-specific walkthrough)
• Live Streaming on AIOZ Stream: The Complete Guide
• Stream Health Metrics Explained
• How to Embed the AIOZ Stream Player on Your Website
• HLS vs WebRTC: Which Streaming Protocol Should You Choose
• What Is Low-Latency HLS (LL-HLS) and When to Use It
• Upload-Only vs Full-Access API Keys