ProPresenter can supply the presentation screen, camera inputs and audio for a live production, then send the selected output to an RTMP destination or its documented Resi integration. It is one part of the workflow: you still need to decide what viewers should see, how sound reaches the stream and which destination accepts the feed.
Start by planning the output rather than opening menus at random. ProPresenter's reviewed user guide identifies its coverage as current through version 7.12, so treat menu names and compatibility details below as a map, not a promise that every control looks the same in your installed release. Check the current guide and your hardware documentation before making a purchase or relying on a particular menu path.
Plan ProPresenter's role in the production
Write down what the remote audience should receive: presentation content alone, camera video, or a combination. Then trace how each part will reach ProPresenter and how its selected output will reach the streaming destination. This avoids the common mistake of treating “go live” as a single button when the picture, audio and destination each have their own decisions.
ProPresenter distinguishes configured Audience screens from Stage screens. Audience screens are intended for the room-facing presentation, including slides and media; Stage screens are designed to show information to people on stage. An output connects a configured screen to a physical or digital destination. Capture Settings can select an Audience or Stage screen, but the documented capture workflow captures one ProPresenter screen at a time. Renewed Vision's screen configuration guide explains the distinction.
That one-screen limit matters when you plan a composite. If the stream needs lyrics and a camera together, arrange the desired composition on the screen you intend to capture rather than assuming the capture feature will combine separate Audience and Stage outputs. Check which Look and layers are active on that screen; an operator display that helps performers may not be appropriate for viewers.
Make a small signal-flow sketch. For example: presentation media and a camera input enter ProPresenter; a dedicated console mix supplies audio; the configured Audience screen and audio route are captured; the selected destination receives the stream. Your own path may be simpler. A devotional channel built around a prepared visual loop may not need a camera, while a local event may need a camera but no slide deck.
It also helps to decide whether this is an event production or a continuous channel. ProPresenter's documented stream workflow is a production output, not a reason to assume that an event-oriented computer and operator workflow will suit an unattended 24/7 channel. If a computer-based encoder is part of the plan, compare that operating burden with the options in our guide to streaming a pre-recorded playlist. Choose according to what must stay live and who will monitor it.
Configure the screen you intend to capture
In the documented workflow, screens are configured through Screens > Configure Screens, and Capture Settings are available through Screens > Capture Settings or the Live button. The precise labels and arrangement can change between releases, so confirm them in the guide for your installed version. The important task is to select a configured screen whose content matches the intended stream.
Check the screen's destination and content before you select it for capture. An Audience screen may be mapped to a projector, another display, or a digital output. A Stage screen may contain confidence information, notes or other performer-facing material. The captured screen is what the remote audience receives; do not infer its content from what happens to be visible on the operator's computer display.
Review the Look and layers currently active. A slide can be correct while an unexpected background, lower third, media layer or stage element remains on screen. If your production uses more than one Look, rehearse the transitions and confirm that the stream-facing screen follows the intended one. Make sure a holding slide or break screen is available if the audience should not see an operator's desktop while you prepare the next item.
Capture Settings lets you choose the source screen and adjust capture parameters for the destination. Avoid relying on an assumed resolution or frame rate: choose settings that the output path and destination accept, and verify the current requirements with their official documentation. The reviewed ProPresenter guide supports the screen-selection workflow but does not establish every destination's current ingest settings.
Before a show, inspect the result in the capture preview and, where available, confirm what the destination is receiving. A local preview can tell you that ProPresenter is capturing, but it cannot by itself prove that the remote platform has accepted the feed or that viewers hear the right mix. Keep a separate check at the destination in your rehearsal plan.
Presentation only or presentation plus camera
A presentation-only stream is usually the simplest path when slides, lyrics, artwork or prepared video are the whole programme. You can use a configured Audience screen and avoid adding camera equipment or another live source. Simplicity does not remove the need to check audio: media embedded in a presentation and audio from a console can follow different routes.
Add camera video only if it contributes something the presentation cannot provide, such as a speaker, a worship leader or a view of a local event. ProPresenter's documented video input workflow requires adding and configuring the video input first; connecting a camera to the computer is not sufficient. The input can then be used from the Video Input Playlist or triggered on a slide or action. See Renewed Vision's video input instructions for the supported setup concepts.
When camera and slides need to appear together, design the layout and check that both sources are visible on the screen selected for capture. Test transitions between a full camera view and presentation content as well as any picture-in-picture composition you plan to use. Verify how your chosen input behaves when it is disconnected or unavailable; a black frame can be more distracting than a deliberate holding slide.
A camera is not a universal requirement, and neither is a particular model or capture device. The right question is whether the camera's output, the computer's ports and operating system, the input method and the intended video format are compatible as a complete chain. If you have no camera source to include, skip this setup rather than buying hardware to satisfy an imagined requirement.
For a camera-led event, also decide who will operate the sources. ProPresenter can make configured inputs available to the presentation workflow, but rehearsing the cue sequence is still the production team's job. Try every transition at the pace you expect during the event, including returning to a slide after the camera shot. This catches layout or routing surprises while there is still time to fix them.
Choose an input path that fits your equipment
Renewed Vision documents several families of video input: USB capture devices, SDI interfaces, NDI sources and Syphon on macOS. These are alternatives, not a shopping list. The appropriate route depends on the output available from the camera or source, the computer and operating system, the connections already in use, and the quality and format you intend to send.
| Input path | When it may fit | What to confirm |
|---|---|---|
| USB capture device | A source provides a compatible video output and the production uses a USB capture path | Supported format, connectors, operating system, and recognition by the installed ProPresenter release |
| SDI interface | The production already uses SDI equipment or needs that type of connection | Interface compatibility, required connections and supported format across the whole chain |
| NDI source | Video is available as an NDI source on the production network | Network configuration, source availability and compatibility with the installed system |
| Syphon | The video source and ProPresenter workflow use Syphon on macOS | Current operating system and application support for the intended source |
These categories do not certify a particular product. Renewed Vision's instructions give examples of USB capture and SDI devices, but an example in a guide is not a guarantee that every model, computer or resolution will work. Check the manufacturer's current compatibility information and ProPresenter's current documentation for the actual devices you plan to use. If a device is not recognised, resolve that before building the show around it.
After choosing a route, open ProPresenter's Inputs settings and add a Video Input using the control names available in your release. Select the source and configure associated audio only if that source is meant to supply sound. Confirm that video is visible in the input workflow, then try using it in the playlist or on a slide as planned. Rebooting or reconnecting on event day is not a substitute for this check.
Keep an eye on what else uses the same connection or network. A production with an NDI source, for example, depends on the source being discoverable and the network path behaving as expected; a direct capture connection has its own cabling and recognition checks. Do not assume that changing one component leaves the rest of the chain unaffected. Record the working connection and settings so another operator can restore them.
Route clean audio to the stream
Decide what the stream should hear before selecting capture channels. The choices may include audio from ProPresenter media, a dedicated console mix, or both. A room mix that sounds right through loudspeakers does not necessarily translate to a stream: the room may add reverberation, and the console may route presentation playback in a way that becomes doubled if the same sound is also captured directly.
ProPresenter capture settings include audio routing controls. Renewed Vision's example for simultaneous house and stream sound assigns the console return to internal channels 3 and 4, then selects those channels for stream capture and disables channels 1 and 2 to avoid doubling playback audio in that particular topology. This is an example, not a universal channel prescription. Your console, interface and ProPresenter routing may be different, so map the signal flow you actually use.
A useful rehearsal is to test each source separately: a voice, presentation media and any camera audio that is intentionally included. Listen at the destination or with a recording from the same capture path. Check that speech is understandable, media is not repeated, and transitions do not leave an unintended source open. If the room and stream need different balances, ask the audio operator to prepare a dedicated stream mix rather than assuming the house mix will suit both.
Also check synchronisation. A voice that arrives noticeably before or after the image makes an otherwise clean stream difficult to follow. The capture preview and a remote playback check can reveal problems that are not obvious at the console. If audio levels vary between spoken sections and music, our guide to keeping podcast audio levels consistent covers useful level-management principles, although a live console mix still needs its own rehearsal.
Write down which channels are captured and why. This is especially useful when several people operate the system or when a room's routing changes between events. Do not copy a channel assignment from a support example without checking whether the corresponding channels in your setup carry the same signals.
Connect to RTMP or the documented Resi integration
ProPresenter 7 documentation describes direct RTMP streaming and recording, as well as an additional Resi integration. RTMP is a destination route, not a guarantee that a particular social platform's current setup will accept your feed. Obtain the current server address, stream key and format requirements from the destination's official instructions. Treat the key as a credential: enter it only in the appropriate application and do not expose it in a screenshot, public message or recording.
In ProPresenter's Capture Settings, select the intended screen, set the capture parameters and configure the destination using the current provider details. Renewed Vision describes starting capture from Capture Settings, the Live button or Screens > Start Streaming; confirm the corresponding controls in your installed version. The progress indicator in the Preview window can show capture activity, but still check the destination separately for receipt and playback.
For YouTube, use YouTube Help's live streaming guidance and current live control-room instructions for account eligibility, stream setup and credentials. These requirements and interface details can change. The reviewed ProPresenter guide documents RTMP generally; it does not validate current provider-specific ingest steps for YouTube, Facebook or another named platform. If you need to publish to more than one platform, establish how each destination is served rather than assuming a single RTMP configuration covers all of them.
The documented Resi route is different: ProPresenter sends the stream to Resi for processing and delivery to destinations configured there. Renewed Vision's guide covers selecting Resi after the integration and account setup, but check Resi's own documentation for current account requirements, destination options and service terms. An account or particular delivery arrangement should not be assumed to be necessary for every production; choose this path only if it fits your distribution plan.
Compare the destination routes by compatibility, account requirements, delivery needs and the process for checking a failed connection. RTMP may suit a destination that provides ingest details; Resi may fit a workflow that uses its documented integration and configured delivery. Neither description settles current pricing or terms, and this article does not make a service comparison. Confirm those details directly before committing.
Rehearse the whole path before going live
A rehearsal should cover the complete signal path, not just whether ProPresenter can start capture. Select the stream-facing screen and check the active Look, layers and slide content. If you use camera video, verify that the input is recognised and that transitions behave as intended. Then listen to the stream mix and check sync at the destination or in a recording made through the same route.
Start the stream in time to discover a problem before the event begins. Confirm that the destination receives the expected picture and sound, and that any stream key or destination details remain private. Keep a simple written checklist for the operator: selected screen, active content, video input, audio channels, destination and a way to verify reception. A checklist is useful because these are separate failure points, not because any workflow can guarantee a flawless broadcast.
If the production is an event with an operator present, decide who watches the destination and who can change the ProPresenter output. If your goal is a continuous 24/7 channel built from a prepared file, the demands are different: ProPresenter's capture workflow should not be treated as a guarantee of unattended recovery. For that use case, read about how auto-restart should work for a 24/7 stream and choose an operating approach that matches the attention you can provide.
Keep version and compatibility checks current
The reviewed user guide identifies its coverage as current through ProPresenter 7.12. That is a boundary on the material reviewed, not evidence that every menu, device or service detail remains unchanged. Renewed Vision's ProPresenter user guide is the place to check current instructions for the installed release, while device manufacturers and destinations should confirm their own compatibility and ingest details.
Before a production change, check the version running on the actual computer and compare the guide's instructions with what is installed. This matters if you are following older support material for RTMP or audio routing: documented feature history does not establish the current names or exact layout of menus. Likewise, a list of input families does not prove that a particular camera, interface, operating system or video format works together.
Test one change at a time when troubleshooting. If video disappears, check source recognition and input selection before changing the capture destination. If audio is missing or doubled, trace the channel routing and identify whether media reaches the console and capture path twice. If the destination does not receive the stream, verify its current ingest details and credentials. This order keeps the diagnosis tied to the component that may have changed.
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
How do I stream with ProPresenter?
Configure the screen you want viewers to receive, choose it in Capture Settings, route the intended audio, and configure an RTMP destination or the documented Resi integration. Rehearse the complete path and verify reception at the destination; menu details should be checked against your installed version.
How do I add a camera to ProPresenter?
Add and configure a Video Input in ProPresenter's Inputs settings, then use it in the Video Input Playlist or on a slide or action. Which connection works depends on the camera output, computer, operating system and compatible input path, so confirm those details before buying or relying on equipment.
How do I get ProPresenter audio into my livestream?
Select the capture audio routing that corresponds to your intended stream mix. The right channels depend on whether sound comes from presentation media, a console return or both; test for doubled audio, level and sync in a rehearsal.
Can ProPresenter stream to YouTube or Facebook?
ProPresenter documents RTMP streaming, but the reviewed guide does not confirm current provider-specific ingest steps for either platform. Check each platform's current official instructions for destination details and account requirements before configuring the stream.