For one HD output, AWS Elemental MediaLive has no single price: your Region, channel class, input and output settings, running time, and optional features all affect the bill. AWS publishes example hourly rates that help frame the processing cost, but they are not a quote for your setup.
The looping YouTube playlist adds a separate unknown. Before estimating an end-to-end total, you need to identify what plays and repeats the playlist and how that source connects to MediaLive; the published MediaLive rates do not establish either the method or its cost.
Why one HD output has no single MediaLive price
“One HD output” describes only part of a channel. MediaLive pricing depends on the channel’s input and output configuration, its class, and its Region. The word “HD” is not enough to identify a billable configuration: input type, codec, bitrate and resolution matter, while output codec, resolution, frame rate and rate-control settings can matter too.
Runtime and resource state also matter. AWS charges for configured inputs and outputs while a channel is running. A channel can incur charges even when an attached input is not active or receiving content, and an output can remain chargeable while paused. Stopping the channel changes it to an idle state, but does not mean every associated charge disappears.
So the practical question is not simply “What does one HD output cost?” It is “What will the specified input, channel class, output and optional features cost in my Region for the hours I intend to run them?” That is a workload estimate, not a universal per-output figure.
If you are comparing cloud encoding with a computer you already own, include the cost of keeping that computer and its connection available overnight. Our guide to running two 24/7 YouTube streams from one computer helps explain the trade-off between sharing local resources and paying for a separate cloud workflow.
AWS’s illustrative input and output rates
AWS’s Live Streaming on AWS deployment guide gives example rates for US East (N. Virginia): $0.234 per hour for an HD AVC input at 10–20 Mbps, and $0.88 per hour for an HD AVC output at 1280x720p or 1920x1080p. Together, those two figures total $1.114 per hour for that example input-plus-output combination. They are illustrative rates, not a quote for the title’s unspecified channel. See the AWS deployment guide’s planning and pricing example.
The example has assumptions beyond the phrase “one HD output”. It is for a particular Region and uses the guide’s specified input and output characteristics, standard pricing, and no free-tier or discount assumptions. The guide’s example also describes a larger deployment profile. It is useful as a transparent anchor, but it does not resolve the exact bill for a single channel built to your requirements.
| Example component | AWS guide’s illustrative rate | What the figure describes |
|---|---|---|
| HD AVC input | $0.234/hour | Input at 10–20 Mbps, under the guide’s assumptions |
| HD AVC output | $0.88/hour | Output at 1280x720p or 1920x1080p, under the guide’s assumptions |
| Input plus output | $1.114/hour | Arithmetic sum of those two illustrative rates only |
These rates are from AWS’s guide; the research material does not state the guide’s revision or publication date, so no date is assigned to the figures here. Check the current AWS pricing documentation and the current guide before budgeting. AWS’s MediaLive pricing documentation explains the billing model, while a live estimate still needs the settings you plan to use.
What the example total does—and does not—include
The $1.114 figure is the sum of one example input rate and one example output rate. It is not an end-to-end hourly cost for a looping playlist, a promise that your channel will use those rates, or a quote from AWS for one HD YouTube stream. Do not multiply it by your planned monthly hours and treat the result as a complete bill without checking the configuration and the workflow around the channel.
The arithmetic also does not price the process that produces and repeats the playlist, the connection from that source into MediaLive, or any downstream delivery and service components not represented by those two line items. The research for this article did not establish a playlist-looping method or the associated costs. That gap matters: a total that silently assumes the playlist is hosted or looped by MediaLive would go beyond what the example establishes.
AWS says there is no channel charge for a running channel, but that statement is not the same as saying a running channel is free. Its inputs and outputs are billable, and optional features may have charges. The AWS pricing page is the place to check the current resource-state rules and any applicable add-ons rather than reading “no channel charge” in isolation.
For a 24/7 channel, use your actual intended runtime, but separate that multiplication from the question of which rates apply. A continuous schedule tells you how long resources may be in a given state; it does not determine the Region, class, input, output or playlist source. Keep those assumptions visible in a worksheet so that a change in one is not mistaken for a change in another.
Configuration details that change the estimate
Start with Region and channel class. AWS distinguishes single-pipeline and standard two-pipeline channel pricing; the rates for one class should not be assumed to describe the other. Choose the Region where you intend to run the channel and check that Region’s current rates. A figure from N. Virginia is not automatically the right rate for a channel deployed elsewhere.
Next, specify the input as a real source, not merely as “HD”. Identify its type and the codec, resolution and maximum bitrate that the service will be configured to use. AWS states that billing follows the input options specified. If you set an HD input specification for an SD source, the input can be charged at the specified HD level rather than at a lower level inferred from the actual source. AWS’s input specification guidance is relevant when checking those settings.
Then describe the output. Record the codec, resolution, frame rate and rate-control settings you expect to configure. “720p” or “1080p” alone may omit details needed to select a rate. AWS documents that output characteristics, including codec and frame rate, affect output pricing; resolution and rate-control configuration can also change the estimate. Its video encode rate-control guidance can help you identify the settings to carry into a pricing check.
Finally, list optional features and the states you expect resources to occupy. Attached inputs can be billed on a running channel even if they are not the active input. Pausing an output does not necessarily stop its charge. A non-running channel has idle charges for inputs and outputs, and some idle push-input cases can also incur charges; AWS says idle pull inputs do not. This is why “stop it when not needed” is not a sufficient cost model by itself.
If you are used to streaming through OBS, the setup may feel different because the cloud service’s bill tracks configured resources as well as the visible programme. Our article on OBS switching between videos automatically covers a local playlist-style workflow; it is useful background for the playback question, but it does not establish how a playlist source should connect to MediaLive.
The unresolved playlist playback and connection costs
A playlist that loops needs a playback source somewhere. That source must provide media to the encoding workflow, and the workflow must deliver the resulting live stream to YouTube. The research sources establish MediaLive pricing and describe a live workflow boundary between upstream content and downstream systems. They do not establish which tool or service should play a looping playlist for this particular setup, how it connects, or what that component costs.
Keep three questions separate when speaking to a provider or planning the architecture: what will play and repeat the files, how will that source feed the encoding channel, and what will carry the encoded live output to YouTube? Until those are answered from current official documentation for the chosen tools, the playlist’s method and cost remain unresolved. Do not assume that MediaLive hosts the video files, repeats a playlist, or provides a YouTube-ready loop simply because it appears in the proposed workflow.
This distinction is useful even if you already have a playlist. A YouTube playlist that organises public videos on a channel is not, by itself, evidence of a continuously generated live input. The playback process that turns selected files into a live feed is a separate operational requirement. You can read about pinning a YouTube playlist to your channel homepage, but that is a channel-navigation feature, not proof of an encoding source or looping method.
The safest estimate therefore has at least two layers: the MediaLive processing estimate for the specified input, channel and output; and a separate, still-to-be-verified source-and-connection estimate. If a vendor or tool is proposed for the latter, check its own current documentation and pricing rather than filling the gap with a guessed cost. Also verify the current YouTube live-streaming requirements for your intended workflow before treating the design as ready to operate.
Build a workload-specific estimate
Make a short configuration sheet before opening a pricing calculator or asking for a quote. Write down your Region, channel class, input type and settings, output settings, expected run hours, optional features and whether you intend to stop, pause or leave resources idle at any point. A provider can only price a described workload; “one HD output” leaves too many choices open.
| Estimate field | What to write down | Why it matters |
|---|---|---|
| Region and class | Deployment Region; single-pipeline or standard | Rates depend on where and how the channel is configured |
| Input | Type, codec, resolution and maximum bitrate | Input billing follows the specified input options |
| Output | Codec, resolution, frame rate and rate control | Output characteristics affect the applicable rate |
| Runtime and state | Planned running hours; pause and idle periods | Running, paused and idle states do not all bill alike |
| Optional features | Add-ons or reservations under consideration | Additional features or commitments can alter cost and flexibility |
| Playlist workflow | Playback source, connection path and verified charges | This is not priced by the two example rates |
Use AWS’s current pricing material for your selected Region and configuration, then calculate the MediaLive component separately from any playlist source or connection component. Preserve the assumptions alongside the result: for example, an estimate that assumes a standard channel and one input is not transferable to a single-pipeline channel or a different input merely because both outputs are HD.
Reservations deserve a separate decision rather than an automatic discount line. AWS says reservations can lower rates for matching configurations, but they involve a one-year commitment, monthly allocation and unused minutes being forfeited at month end. Matching depends on configuration attributes such as codec, resolution, bitrate range, output frame-rate range and Region. If your schedule or settings may change, compare the commitment against the workload you genuinely expect; do not count a possible saving until you have checked the match and terms on the current AWS reservations guidance.
For readers who do not want to keep a computer running to send the same uploaded video continuously, StreamNeo removes that specific always-on computer task by turning an uploaded video into a YouTube live stream that continues without your computer switched on. It does not answer the MediaLive pricing question or establish a playlist source workflow, so keep the two decisions distinct.
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
Is $1.114 per hour the price for one HD MediaLive output?
No. It is the arithmetic sum of AWS’s illustrative HD AVC input and output rates in its N. Virginia deployment-guide example. Your Region, class, input and output settings, runtime and features may differ, and the figure does not include an established playlist source workflow.
Does MediaLive loop the YouTube playlist?
The sources used here do not establish a playlist-looping method or that MediaLive hosts or repeats a playlist. Identify the playback source and connection path, then verify them against current documentation for the tools involved before relying on an end-to-end design.
Does stopping a channel make the cost zero?
Not necessarily. AWS documents idle charges for channel inputs and outputs, as well as charges for certain idle push inputs; it says idle pull inputs do not incur that idle charge. Check the current billing rules for your resource types and states rather than assuming stopped means free.
Can reservations reduce the cost?
They may reduce rates for a matching configuration, but AWS describes a one-year commitment and monthly minutes that are forfeited if unused. Check the exact match conditions and compare them with your likely operating hours before treating a reservation as a saving.