LinkedIn Live works with Wowza, but the setup depends on which Wowza product you use. Wowza Video has a LinkedIn destination integration; Wowza Streaming Engine uses a separate manual RTMPS configuration. In either case, schedule a LinkedIn event first and check its preview before you make the broadcast public.
This guide walks through both routes without mixing their controls or credentials. LinkedIn no longer offers spontaneous live broadcasts, so even a short test or last-minute stream needs a scheduled event.
First identify your Wowza product
The labels matter because the setup screens and connection details differ. Wowza’s current cloud instructions are for Wowza Video. They describe adding LinkedIn Live as a destination to an output rendition in a Wowza Video stream. If you manage streams through Wowza’s cloud product and see a Components tab, that is the route to follow.
Wowza Streaming Engine is a different product. Its LinkedIn workflow is a manually configured RTMPS target: you enter connection details in the Engine’s streaming configuration rather than adding a LinkedIn destination through Wowza Video. Wowza has a separate Streaming Engine guide for LinkedIn Live. Use that guide for the Engine-specific fields; don’t assume that instructions for the Video integration map one-to-one onto them.
If you are unsure, check the name shown in the product interface and the way your stream is managed. A cloud stream with a Components tab points towards Wowza Video; a server installation administered through Streaming Engine points towards the manual configuration. If neither description fits, confirm your product and version with Wowza before changing a working stream.
Also confirm that the LinkedIn member or Page you plan to use is eligible to host a Live event. For a Wowza Video destination aimed at an organisation Page, Wowza says the LinkedIn account used to authorise the connection must be an administrator of that Page. A missing permission can look like a configuration problem even when your source stream is healthy.
Choose the destination route that fits
With Wowza Video, the LinkedIn destination integration is the more direct path: authorise LinkedIn, choose the profile or organisation, set destination details and save. Wowza manages the destination as part of the Video stream’s configuration. This is appropriate when you want to use the cloud product’s supported integration and its available LinkedIn options.
With Streaming Engine, configure LinkedIn as a manual RTMPS target using the event’s connection details. This route gives you the Engine’s host, port, application and stream-name fields to complete, including SSL settings as described in Wowza’s Engine guide. It is not the same as authorising an account inside Wowza Video, and credentials from one route should not be substituted into the other without explicit product guidance.
| Route | Where you configure it | What you need to prepare | Best fit |
|---|---|---|---|
| Wowza Video destination | Components in the Wowza Video stream | LinkedIn authorisation, destination selection and event details | A cloud stream using Wowza Video’s LinkedIn integration |
| Streaming Engine manual RTMPS | Streaming Engine target configuration | LinkedIn event URL and key, then the Engine-specific target fields | An Engine stream managed through its manual output settings |
The same LinkedIn event still needs preparation whichever route you choose. LinkedIn’s custom stream instructions explain how to create a scheduled Live event, obtain the Stream URL and Stream Key, and inspect the preview. For recurring organisation Page broadcasts, a persistent key may reduce repeated credential entry, but it has restrictions discussed below. For a one-off event, the ordinary event-specific credentials are the straightforward choice.
A scheduled event is not just an administrative detail. It creates the destination context in which LinkedIn provides the URL and key and gives you a preview before the public broadcast begins. Build your checklist around that boundary: connecting a feed and seeing it in preview are not the same as clicking Go live.
Create or schedule the LinkedIn event
LinkedIn ended spontaneous live broadcasting on 22 June 2026. You now need a scheduled event, even if you only schedule a few minutes ahead for a short-notice stream. Older guides that begin with a direct “Go live now” step no longer describe the current process. Check LinkedIn’s notice about the change to Live events if your interface or an older tutorial suggests otherwise.
Create the event for the profile or organisation that should publish it, and make sure the account you use has the permissions needed to manage that destination. Add the event’s title, description and timing, then open Live Studio’s Manage streams area when its controls become available. LinkedIn’s preparation window depends on account type and verification: verified Pages can prepare up to two hours before the start, while unverified Pages and profiles can prepare one hour before.
The event’s scheduled time is not necessarily the exact moment you must begin the public broadcast. LinkedIn’s guidance allows a scheduled event to go live from 15 minutes before its time through two hours after its scheduled start. If a test or setup issue pushes you outside that window, check the event controls and LinkedIn’s current help rather than assuming the event can still be started.
It helps to separate three actions in your notes: create the event, connect and test the feed, then publish by selecting Go live. Keep the last action with whoever is responsible for making the content public. If a colleague is testing the signal, agree in advance that they should stop at preview and not press the public control.
Find the credentials and configure the right product
In Live Studio’s Manage streams, open the scheduled event’s preparation controls. Choose the ingest region, then generate or retrieve that event’s Stream URL and Stream Key. Copy them carefully into the workflow for your Wowza product. Treat the key as a password: share it only with people configuring the stream and avoid leaving it in public notes or screenshots.
For Wowza Video, open the stream and go to Components. On the highest output rendition, open the menu and choose Add LinkedIn Live. Authorise Wowza with the LinkedIn account that can publish to the intended profile or Page. Select the destination, enter the requested event details, choose the region closest to the Wowza Video stream’s broadcast location and save the configuration. Wowza’s Video setup guide shows this product-specific route.
For Streaming Engine, follow its manual target setup. Enter the LinkedIn-provided RTMPS information into the relevant host, port, application and stream-name fields, and configure SSL as the Engine guide specifies. Choose a LinkedIn region close to the Streaming Engine instance, rather than copying the region choice from a Wowza Video setup. The field names can make the two workflows sound similar, but the integration steps are not interchangeable.
For regular events on an organisation Page, LinkedIn offers a Persistent Stream Key. A Content or Super admin must enable it, and personal profiles cannot use it. The persistent key can be reused across scheduled Page events until it is reset, but only one event can use it at a time. If you need two simultaneous events, use the ordinary event-specific key for the second one. Confirm that the Page’s permissions and the event arrangement suit this option before changing a repeatable workflow.
A credential mismatch is one of the first things to check if the destination refuses a feed. Verify that the event is the one you intend to use, that its URL and key were copied as a pair, and that you entered them into the correct product route. If you regenerated a key, update the configured destination rather than relying on an older saved value.
Match the source to LinkedIn’s requirements
Before testing, check what your source can actually output. Wowza’s LinkedIn Video guide lists a maximum of 1080p (1920 × 1080) at 30 frames per second, with an I-frame at least every two seconds. It gives recommended maximums of 6000 Kbps video and 128 Kbps audio at a 48 kHz sample rate. These are published vendor settings, not a promise that every source or network will behave identically; LinkedIn may change its requirements, so verify its current encoder guidance before an important event.
| Setting | Wowza’s published LinkedIn guidance | What to check in your source |
|---|---|---|
| Picture size and frame rate | Up to 1080p (1920 × 1080) at 30 frames per second | The selected output rendition does not exceed either value |
| I-frame interval | At least one I-frame every two seconds | Encoder keyframe interval is set to meet this requirement |
| Video rate | Recommended maximum 6000 Kbps | The configured video bitrate is within the stated maximum |
| Audio | Recommended maximum 128 Kbps at 48 kHz | Audio rate and sample rate are both supported |
| Live duration | Maximum four hours | The event is short enough for LinkedIn Live’s stated limit |
The highest output rendition is not automatically the best choice if it exceeds a requirement or your connection cannot sustain it. Choose a rendition that fits both LinkedIn’s limits and the available upload capacity at the source. A clean 720p output that stays stable is more useful than a larger stream that repeatedly loses its feed.
The four-hour maximum is especially important if your normal format is an always-on channel. Wowza says 24/7 streams are not compatible with LinkedIn Live because of this duration limit. If your broader publishing plan involves a continuous channel, keep LinkedIn as a scheduled, finite event rather than assuming a YouTube-style overnight loop can run there. For a separate YouTube workflow, the practical notes in running a 24/7 Ram bhajan stream from India address a different platform and operating pattern.
Preview first, then publish deliberately
Once the destination is saved, start the Wowza stream to send the feed to LinkedIn. In Live Studio, wait for the incoming signal and inspect the preview. Check that the picture is moving, the sound is present and in sync, the correct event is open, and no unintended test slate or private material is visible. A visible preview means LinkedIn is receiving a feed; it does not make the event public by itself.
LinkedIn limits the time available for preview. Verified Pages can preview for up to two hours, while unverified Pages and profiles have up to ten minutes. Plan the check rather than starting too early and leaving the source running while you troubleshoot unrelated details. Resolve titles, graphics, audio levels and the event description before opening the preview window where possible.
When you are ready to broadcast, confirm with the person responsible for the event and click Go live in LinkedIn. Do not use that control just to see whether the connection works. After the public portion is complete, end the stream in LinkedIn as well as stopping the source in Wowza, then confirm the event has finished as intended.
A preview-first habit is useful even when your source is a prerecorded loop rather than a presenter. For example, if you are testing a playlist and an end card appears between files, catch it in the preview before the event is public; our guide to keeping a YouTube loop from showing an end screen covers that specific YouTube behaviour, while the LinkedIn preview is where you check the actual LinkedIn output.
If a colleague operates the encoder while you manage the event, agree on a simple hand-off: the operator reports a clean preview, and the event host alone decides when to publish. That avoids accidental broadcasting during sound checks or while correcting a title. If the test needs more time than the permitted preview window, schedule a separate test event rather than treating the public event as an unlimited sandbox.
Troubleshoot a stream that will not connect
Start by identifying where the failure occurs. If Wowza cannot save or authorise the destination, check the product route, LinkedIn account permissions and destination selection. If Wowza is sending but Live Studio shows no incoming feed, check the event credentials, ingest region, output settings and network path. If the preview appears but is unstable, focus on bitrate, upload capacity and connection quality before changing unrelated event details.
LinkedIn recommends a wired connection for stream health and says its troubleshooting guidance recommends at least 10 Mbps upload speed. Treat that as guidance to check against the whole connection, not as a guarantee: other traffic on the same connection can reduce what is available to the encoder. An Ethernet cable is useful when your equipment and location support it, but it is not a required purchase for every setup.
For an ingest failure, LinkedIn says RTMPS ports 2935 and 2936 should be available. If the stream reaches the platform but processing fails, LinkedIn suggests trying the Baseline video profile; High or Main profiles can introduce B-frames and timestamp problems. If a selected region appears overloaded, try another nearby region. Make one change at a time and check preview again so you know which change mattered.
For recurring disconnects, first stabilise the source and its connection rather than increasing every quality setting. A lower rendition can reduce the load on a constrained upload path. If your normal YouTube source configuration is built for long unattended sessions, remember that LinkedIn’s four-hour limit and scheduled-event model are different constraints. Notes from making a YouTube music stream reconnect automatically with FFmpeg can help frame reconnect planning for YouTube, but they do not replace LinkedIn’s event-specific checks.
Once the feed is stable, avoid repeatedly regenerating credentials unless needed; every regeneration creates another value to track and re-enter. Keep a private record of which event, region, product route and rendition were tested. If a known-good configuration stops working, compare those specific details first and consult the current LinkedIn and Wowza documentation, since interface labels and ingest requirements can change.
If the work is a fixed prerecorded video intended to loop unattended, the platform choice is worth settling before configuring the event. StreamNeo turns an uploaded video into a YouTube live stream, so it can remove the need to keep a computer running for a YouTube loop; it does not send to LinkedIn, and LinkedIn’s scheduled-event and duration rules still apply to this setup.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I stream from Wowza Video and Wowza Streaming Engine the same way?
No. Wowza Video uses a LinkedIn destination integration in the stream’s Components tab, while Streaming Engine uses a separate manual RTMPS target configuration. Follow the guide for the product you actually operate, and do not copy one product’s setup assumptions into the other.
Can I test the stream without making it public?
Yes. Start the source and inspect the incoming feed in LinkedIn Live Studio’s preview, but do not select Go live during a test. The preview window is time-limited, so prepare the event and production checks before opening it.
Can I reuse a LinkedIn Stream Key for every event?
Not every account or event uses the same credential workflow. LinkedIn’s Persistent Stream Key is for organisation Page events, must be enabled by a Content or Super admin, cannot be used on a personal profile, and supports only one event at a time; otherwise use the event-specific key.
Can LinkedIn Live run as a 24/7 stream?
Wowza’s published LinkedIn guidance lists a four-hour maximum live duration, so it is not suited to an uninterrupted 24/7 broadcast. Schedule a finite event and verify the current limits with LinkedIn and Wowza before going live.