Wirecast’s output resolution and bitrate are set through the encoder preset selected for your YouTube destination. Choose a preset that fits the picture you want and the upload capacity you can sustain, then test it before relying on it for a live broadcast.
YouTube’s H.264 figures are recommended ingestion targets, not mandatory settings or a guarantee of stability. Wirecast menus and labels can vary between versions and operating systems, so treat the path below as a guide and check the controls in your installed build.
Where Wirecast output settings live
In Wirecast, look for Output > Output Settings. Select the YouTube destination in the output configuration, then choose an encoder. That encoder and its preset determine the resolution, frame rate, codec and bitrate Wirecast sends; changing the canvas or source shot alone does not necessarily change the outgoing stream format.
The documented workflow comes from Telestream’s Wirecast 16 Windows user guide. Your build may phrase a control differently, or arrange the controls in another place. If the menu path does not match, search the version-specific guide for “Output Settings” or “Encoder Presets” rather than assuming the setting is missing.
Before opening Wirecast, prepare the live event in YouTube Studio. Depending on the workflow, you may need its stream destination and key. Keep the key private: anyone with access to it may be able to send a broadcast to your channel. If you are unsure which value goes where, this explanation of the YouTube stream key and stream URL helps distinguish them.
Choose YouTube and an encoder preset
In Output Settings, choose YouTube as the destination and select an encoder preset that is close to your intended format. A preset is a practical starting point, not a universal recommendation. Check the actual output fields: width and height, frame rate, codec, bitrate mode and bitrate. The available choices depend on the Wirecast version, operating system and encoder in use.
For a straightforward H.264 setup, YouTube’s live encoder guidance specifies RTMP or RTMPS ingestion, recommends RTMPS, and calls for constant bitrate (CBR). It recommends a two-second keyframe interval and says not to exceed four seconds. Use those as configuration guidance for a compatible encoder, while checking what your Wirecast build exposes. YouTube also lists other codecs, but availability in Wirecast can differ. See YouTube’s live encoder settings for the current requirements and recommendations; confirm the live page rather than relying on an old preset name.
The preset should match what you are actually producing. A static devotional image with a spoken introduction has different motion demands from a dance performance or a fast-moving game. Higher resolution preserves more spatial detail, and higher frame rate can make movement smoother, but both can call for more bitrate and encoding work. More is not automatically better if your connection or computer cannot maintain the chosen settings.
YouTube normally detects a live stream’s resolution and frame rate automatically. If you have a specific reason to set them manually in YouTube Studio, its guidance is to create a custom stream key and enable manual settings under Stream Resolution. Do not assume that selecting a Wirecast preset alone changes this YouTube-side setting. Details are on the manual stream resolution help page.
When to copy and edit a preset
If the available preset is close but not right, copy it and edit the copy rather than altering a shared default. In the documented Wirecast 16 Windows workflow, Encoder Presets controls let you copy a preset, change its settings and save it with a new name. Other builds may use different labels or offer different fields, so consult the guide for your version before following the exact clicks.
Give the new preset a name that records its intended use, such as “YouTube H.264 720p 30”. This makes it easier to recognise during a later session and reduces the chance of choosing a format meant for another production. Set the dimensions and frame rate to the output you need, then set the bitrate and mode supported by that encoder. If an option called Strict Constant Bitrate is available, Telestream describes it as holding the configured average bitrate strictly; it is a choice to understand, not a cure for an inadequate upload connection.
Keep the original preset unchanged so you can return to it if an edit behaves unexpectedly. After saving, select the copied preset for the YouTube output and verify that it is the one actually active. A change saved in the preset editor is not useful if the output is still assigned to a different encoder.
Resolution also interacts with the material entering Wirecast. If the source is lower resolution than the output, increasing the output dimensions cannot create missing detail. If the source is high resolution but the programme is mostly static, a lower output may be a reasonable trade-off. The aim is a readable, consistent picture, not a larger number on a settings panel.
YouTube H.264 bitrate targets by resolution and frame rate
YouTube’s published H.264 recommendations provide a reference for common live formats. The figures in the table are YouTube’s recommended ingestion bitrates, not a mandatory minimum, an independently tested result, or evidence that your internet connection can sustain them.
| Output format | YouTube recommended H.264 bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
These values come from YouTube’s current encoder guidance, whose table separates recommendations by codec, resolution and frame rate. The difference between the 1080p rows reflects the higher target published for 60 fps. At 720p, the listed H.264 recommendation is the same for 30 and 60 fps. If you use a different codec or resolution, consult the corresponding row in YouTube’s table rather than extrapolating from these examples.
For “What bitrate should I use for 1080p 60fps?”, 17 Mbps is YouTube’s recommended H.264 target. It is a useful reference when deciding what to configure, but it is not a promise that 17 Mbps is right for every source, encoder, connection or channel. If your upload capacity is constrained or variable, choose a lower format you can test reliably rather than treating the recommendation as an obligation.
Likewise, “Should I use 720p or 1080p for a live stream?” depends on your content and available capacity. A small text overlay may benefit from the extra detail of 1080p; a largely static image may remain clear at 720p. The practical comparison is whether the additional detail is visible to your viewers and worth the greater bitrate demand in your circumstances.
Match bitrate to upload capacity
A speed test gives you an indication of available upload capacity, but a single result is not a guarantee of sustained performance. YouTube advises testing upload bitrate and choosing a quality that is reliable for the available connection. Measure under conditions that resemble the actual broadcast where possible: same network, same connection method, and other usual household or workplace traffic.
Compare the result with the bitrate you intend to send. Your connection also has to carry audio and any other traffic, and its capacity may change while the stream is running. Do not plan to use every last bit of an impressive speed-test result. If the available headroom is small, reduce the outgoing bitrate, resolution or frame rate and test again. The podcast bitrate guide for a 24/7 YouTube stream offers a related way to think about sustained settings for an always-on channel.
| Choice | What it trades | When it may make sense |
|---|---|---|
| 1080p at 60 fps | More detail and smoother motion, with a higher H.264 target than 1080p30 | Fast movement is important and a test shows the connection and encoder can keep up |
| 1080p at 30 fps | Full-HD output at a lower published target than 1080p60 | Detail matters more than smoother motion |
| 720p at 60 fps | Lower dimensions than 1080p, with smoother motion and the same published target as 720p30 | Movement matters, but 1080p is difficult to sustain |
| 720p at 30 fps | Lower dimensions and a modest output format for mostly static content | Stability and legibility matter more than fine detail or rapid motion |
The table is a comparison of options, not a prescription. For a bhajan channel showing lyrics over a still image, 720p30 might be adequate if text remains readable on a phone. For a local news loop with scrolling text, check that the ticker is legible before deciding that a lower resolution is sufficient. Make the choice with a representative test, not only by comparing the numbers.
Bitrate is not the same as data usage in every circumstance, but a higher sustained bitrate generally means more data sent over time. If you are planning an always-on stream on a capped connection, account for that ongoing transfer as well as short-term upload capacity. This guide to data use for a 24/7 YouTube stream is useful when estimating the connection’s longer-term demands.
Test stream health and stability
Run a private or otherwise appropriate test before a public broadcast. YouTube specifically recommends a test with audio and movement similar to the planned stream, then checking stream health and messages. A still test screen will not expose every issue you may see with a moving camera, scrolling captions, music or a busy Wirecast composition.
During the test, watch both Wirecast and YouTube Studio. Check for dropped frames, encoder overload warnings, delayed or missing audio, and YouTube stream health messages. Note whether problems begin immediately or only after the stream has run for a while. A stable preview at the start is useful, but it does not establish that the settings will remain stable through a long programme.
If the picture or connection falters, change one thing at a time so you can tell what helped. Lowering the output resolution or frame rate can reduce the demands on the encoder and connection; a lower bitrate can also ease network demand. Retest the altered preset under similar conditions. Dropped frames do not prove that resolution alone is the cause: the network, computer load, source capture and other parts of the production can all be relevant.
If YouTube reports that it is not receiving data, check the destination, key and connection before repeatedly changing image quality. If the stream disconnects and reconnects, this guide to YouTube RTMP reconnection behaviour covers a related problem from a different streaming workflow; the Wirecast controls themselves may differ. Keep the stream key private while troubleshooting and confirm that the intended event is selected.
For an always-on channel, include a longer representative run in your preflight. Observe whether Wirecast stays responsive and the incoming feed remains healthy while other normal tasks are happening. A short test can help catch a wrong preset or key, but it cannot prove that every future network condition will be the same. Keep notes of the preset name and what you observed so you can return to a known configuration after edits.
A cloud-based broadcast can remove the need to leave your own computer running overnight: StreamNeo turns an uploaded video into a YouTube live stream, so you do not have to keep Wirecast open on a local machine for a file-based loop. It is YouTube-only, and the source file and channel still need to be prepared correctly.
A practical setup sequence
Use a repeatable sequence rather than changing bitrate, resolution and frame rate together. First decide what viewers need to see: a logo and still background, readable lyrics, a text ticker, or fast-moving footage. Then select an output format that matches that content and the capacity you have measured.
Next, select YouTube in Wirecast’s output settings and choose a compatible encoder preset. If you need different values, copy the preset, name the copy clearly and change only the relevant fields. Check YouTube’s published H.264 recommendation for the intended resolution and frame rate, then choose a bitrate in light of your upload conditions rather than assuming you must use the full target.
Run the representative test and inspect stream health. If the test is unstable, step down one setting, save the modified preset under a clear name, and repeat. If the stream is stable but text or detail is difficult to read, try a higher resolution only if capacity permits. This process makes the trade-off visible and avoids treating a single published bitrate as the answer for every channel.
Keep a brief record: preset name, output format, bitrate, test conditions and any YouTube messages. That record is useful if a future change to the network, Wirecast version or programme creates a new problem. It also makes it easier to distinguish a settings change from a change elsewhere in the production.
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
What bitrate should I use for YouTube Live?
Use YouTube’s published table for your codec, resolution and frame rate as a reference, then account for upload capacity and stability. For H.264, YouTube currently recommends 8 Mbps for 720p at either 30 or 60 fps, 14 Mbps for 1080p30 and 17 Mbps for 1080p60. These are targets, not guarantees.
How do I change resolution in Wirecast?
Select the YouTube output and inspect its encoder preset. Edit a copy of a preset to change its dimensions where your Wirecast version and encoder expose those controls, then save and select the copy. Menu names vary, so consult the guide for your installed version.
How do I stop dropped frames on Wirecast?
First check the Wirecast status, YouTube stream health and your connection rather than assuming one setting is responsible. Try reducing bitrate, resolution or frame rate one at a time, then repeat a representative test. A lower setting may help, but it does not guarantee that dropped frames will stop.
What bitrate should I use for 1080p 60fps?
YouTube’s published H.264 recommendation for 1080p60 is 17 Mbps. Treat it as an ingestion target to weigh against your available upload capacity and test results, not as a mandatory value or promise of a stable stream.