Castr’s free trial lasts seven days, and its published trial limits include 5 GB of bandwidth for embeddable-player use and 1 GB of video storage. Those account limits are separate from the maximum duration of an individual YouTube live session: Castr’s reviewed trial documentation does not state a separate session-duration cap, but it also does not promise an unlimited session.
If you are planning a continuous channel, first establish whether you are sending a live encoder or camera feed, or scheduling prerecorded content through Castr TV Playout. The published Loop restriction applies to the latter workflow, not automatically to every YouTube live stream. Check current limits with Castr before relying on a trial for an overnight or multi-day broadcast.
What the seven-day free trial describes
The seven days refer to the trial period for a new Castr account, not a stated run time for each broadcast. Castr’s Help Center article on trial limitations describes the account trial and its allowances. Its “Getting Started” guide says dashboard access ends after the period unless you subscribe. That is a statement about access to the account, not proof that an individual YouTube session is cut off at the seven-day mark.
This distinction matters when you are planning a 24/7 devotional, study, or ambience channel. An account could have a seven-day evaluation period while a particular live session has its own rules, and the two questions need separate answers. The trial page reviewed here does not specify a maximum length for an ordinary live stream sent to YouTube. Do not treat the absence of a stated cap as a guarantee that a stream will continue indefinitely.
Before testing, write down the actual workflow: encoder or camera input, YouTube as destination, planned broadcast duration, and whether you will send one continuous session or schedule files. If you need a continuous stream beyond the trial period, ask Castr support what happens to an active broadcast when trial access expires, and request confirmation for the account and workflow you intend to use. Do not assume that a dashboard deadline necessarily describes exactly how an active session behaves.
YouTube’s own current live streaming requirements and restrictions are a separate consideration. Castr’s account terms do not override YouTube’s rules or guarantee that a broadcast will remain available. Confirm both sides before building a schedule around a long-running stream.
Trial bandwidth and video storage limits
Castr’s trial article states 5 GB of bandwidth for use with embeddable players and 1 GB of video storage. These are account resource allowances, not an announced YouTube audience cap or a fixed number of hours of YouTube broadcast. The bandwidth wording is specifically tied to player delivery, such as a stream embedded on a website. It should not be converted into a claim that a YouTube stream has a given viewer limit or will stop after a calculated number of hours.
Think of these as different resources. Storage relates to video files held in the account. Player bandwidth relates to delivery to viewers through Castr’s player. A direct YouTube broadcast is distributed on YouTube, so the published player bandwidth figure does not by itself tell you how YouTube measures or limits delivery to its audience. If you plan to embed the Castr player on your own site as well as stream to YouTube, player usage is directly relevant and should be estimated.
Castr’s bandwidth calculator uses bitrate, concurrent viewers, and duration to estimate player delivery. Its example says that a 6 Mbps stream uses roughly 2.6 GB per viewer-hour. Treat this as Castr’s planning estimate for player bandwidth, not a YouTube-specific rule or a trial runtime calculation. The calculator also warns that its result does not account for other plan or feature restrictions.
Storage planning is more straightforward but still requires checking file sizes. A set of long prerecorded videos can approach a small allowance faster than a few short clips. Keep the source files locally, note the size of each upload, and ask Castr whether any particular encoding, file-count, or retention restriction applies to your account. Do not infer that the 1 GB figure describes the size or duration of a YouTube live session.
For a small business using a website player, count likely viewers and expected viewing hours as well as the YouTube audience. For a channel using YouTube alone, focus on destination access, input compatibility, session behaviour and trial expiration, then ask which account limits are relevant to that route. If an allowance is important to the test, get the answer in writing rather than inferring it from a calculator.
What is not published about YouTube session duration
The reviewed Castr trial materials do not publish a separate maximum duration for an ordinary live encoder or camera stream sent to YouTube. They also do not establish that such a stream can run without a time limit. The careful conclusion is narrow: the trial article reviewed does not state a YouTube live-session cap. That is a documentation gap, not evidence for either an unlimited session or a hidden seven-day cutoff.
This wording is useful because support answers often get blurred across account, plan and platform limits. Ask Castr specifically whether an ordinary live stream to YouTube has a maximum continuous session length during a trial, whether it differs on a paid plan, and what happens at trial expiry. If you are using a stream key and an encoder, say so. If you are scheduling files through TV Playout, describe that separately, because the relevant restrictions differ.
Also confirm what counts as a disconnect, whether reconnecting starts a new session, and whether a short network interruption needs manual action. These operational questions matter for an unattended channel even if no published duration cap exists. For practical reliability work around a local machine, see this guide to keeping a 24/7 YouTube yoga stream running on a refurbished desktop in India. A local setup has different failure points, but the same habit applies: test the exact route rather than relying on a headline feature.
Castr recommends testing with a private or unlisted broadcast and running the test for as long as the planned event. Its stream testing guide is useful operational advice; it does not mean that the trial automatically includes an uninterrupted session of that duration. Use a test to catch configuration issues, but obtain confirmation about trial access and session limits separately.
Distinguish a live stream from TV Playout looping
A live stream and a playout channel can look similar to viewers, but they are different workflows. In a live encoder or camera workflow, a source sends a continuing feed to YouTube. In TV Playout, you schedule stored media files to make a channel-like sequence. Whether the sequence repeats is a feature of that playout workflow, not a general property of every YouTube broadcast.
Castr’s TV Playout guide says Trial, Starter and Standard plans do not support Loop mode. That statement concerns repeating scheduled content through TV Playout. It is not evidence that a live camera, encoder, or externally generated feed to YouTube has the same limit. Keep the feature distinction explicit when checking account eligibility.
If your plan is to repeat a bhajan playlist, a local news bulletin, or a set of recorded lessons, identify whether you mean a YouTube playlist, an encoder sending a pre-mixed sequence, or Castr TV Playout. The words “continuous stream” can describe any of these, but the product controls and restrictions are not interchangeable. A playlist loop on YouTube may have its own constraints; a playout feature’s Loop mode is a Castr feature; a live encoder session raises the session-duration question discussed above.
For a file-based YouTube workflow, this guide on streaming prerecorded videos to YouTube Live from Google Drive may help you map the chain from source file to broadcast. The main practical point is to name the mechanism when asking support. “Can I run continuously?” is too broad; “Can this trial account send one encoder-fed YouTube live session for the planned duration?” or “Does this plan include repeating scheduled TV Playout?” is answerable.
Check which plan features your workflow needs
Do not compare trial and paid options on a single headline figure. For continuous YouTube use, the useful questions include whether the plan permits the destination count you need, how many streams can run at once, whether your workflow needs stored files, and whether it needs a playout loop. Session duration should be a separate question unless Castr confirms that a published plan feature governs it.
Castr’s pricing page lists paid-plan allocations, but these are not trial allowances. As listed on Castr’s site in October 2026, its monthly-billed Starter listing shows 200 GB per month of player bandwidth, six destinations and two concurrent streams; its annual billing display lists 2.4 TB upfront and three concurrent streams. Check the current pricing page before deciding, since allocations and presentation can change. These figures do not answer how long one YouTube session may last.
| Question | Why it matters | What to verify |
|---|---|---|
| How long is the account trial? | Determines when trial access ends. | Current trial end date and what happens to an active broadcast. |
| Is player bandwidth relevant? | Matters when viewers use an embedded Castr player. | How the account measures player delivery and what happens at the allowance. |
| How much file storage is available? | Affects uploaded prerecorded media. | Current allowance, file restrictions and whether unused files can be removed. |
| Which destinations are available? | A channel may need YouTube alone or several destinations. | Trial destination access and any plan-dependent count. |
| Is this live input or scheduled playout? | TV Playout Loop support is not the same as session duration. | Whether the workflow requires Loop mode and whether the plan includes it. |
| Is a continuous session capped? | This is the central unresolved trial question. | Written confirmation for YouTube, trial status and planned duration. |
The table is a checklist, not a promise that every answer is published in one place. The trial article does not provide a complete current destination count or a full feature-by-feature comparison between trial and paid plans. If you depend on a particular feature, confirm it directly rather than assuming a paid tier or trial includes it from a general plan description.
For an encoder-driven setup, the FFmpeg command guide for 1080p 60fps YouTube Live Streaming can help you think through source settings, though it does not resolve Castr account terms. If you are still evaluating a local machine versus a managed workflow, decide first whether you need a computer to remain on and monitored; the plan table will not answer that operational choice.
Monitor bandwidth and storage use
If you use Castr’s embedded player, estimate usage from the three inputs Castr’s calculator asks for: encoded bitrate, concurrent viewers and viewing duration. A steady stream watched by a few people for long periods can consume more player bandwidth than a higher-bitrate test seen briefly. Recalculate when the audience pattern or bitrate changes. The calculator’s 6 Mbps example is a planning estimate, and should not be treated as an exact bill or as YouTube’s own accounting method.
Keep a simple record during the trial: upload name and file size, stream dates, whether the player was embedded, and approximate concurrent player viewers. That record helps you identify which activity is consuming account resources. Avoid attributing YouTube viewer traffic to Castr player bandwidth unless you are actually serving those viewers through the embedded player.
For storage, keep a separate list of uploaded assets and their sizes. If the channel rotates among several programmes, test with representative files rather than uploading an entire library before confirming the allowance. Delete or replace files only after ensuring that your broadcast workflow no longer depends on them. Ask support whether a file used in a scheduled playout remains subject to the same storage accounting as other uploads.
Paid account behaviour can also differ by tier. Castr says Starter and Standard accounts have streams automatically disabled after allocated bandwidth is exhausted, while Premium and higher plans have overage protection. Castr’s Help Center article dated March 18, 2026 describes a charge after rollover bandwidth is exhausted for those higher paid tiers. This is paid-plan policy, not evidence of trial overage behaviour, and it should not be assumed to apply to a trial account. Check the current wording with Castr before using any overage expectation in your budget.
The practical decision is whether your test is intended to validate broadcast mechanics or measure a real website audience. For the first, use an unlisted YouTube test and watch the stream from YouTube; do not treat player bandwidth as a proxy for YouTube delivery. For the second, include the embedded player in the test and monitor the account’s usage. If the two routes are mixed, label them separately so that a limit is not mistaken for a session-duration problem.
Confirm current trial and upgrade limits
Castr’s trial article was published in 2024, while its onboarding guide was updated in 2026. The available documentation still does not settle a current ordinary YouTube session cap or provide a complete trial destination and feature matrix. Treat the stated 5 GB player bandwidth and 1 GB storage as published trial facts from the trial article, but confirm that the same allowances apply to the account you are opening now.
Before you schedule an unattended event, send Castr a short written description containing the account tier or trial status, destination (YouTube), source method, whether it is live input or TV Playout, planned duration, and whether files or an embedded player are involved. Ask for separate answers on the account trial end, session duration, destination access, storage and applicable bandwidth. Specific questions prevent an answer about TV Playout looping from being mistaken for a rule about a live encoder session.
Then run an unlisted or private test through the same path you intend to use. Confirm that YouTube receives the signal, audio and video remain acceptable, and the broadcast behaves as expected during the test window. A test can reveal configuration or stability problems; it cannot establish a guarantee about a longer session or a future plan change. Keep a fallback plan for an important overnight broadcast, particularly if the event cannot simply be restarted.
If the workflow depends on repeated prerecorded content, test the scheduling and loop behaviour on the intended plan before preparing the full channel. If it depends on a live source, test the encoder, network and destination separately from account billing assumptions. For a 24/7 channel, choosing between a machine that must remain on and a cloud-run file broadcast is also an operational decision; StreamNeo addresses the specific burden of keeping your own computer powered and watched for a prerecorded YouTube channel, but does not change Castr’s terms or YouTube’s rules.
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
Does Castr’s seven-day trial mean a YouTube stream stops after seven days?
No such per-session limit is stated in the reviewed trial documentation. The seven days describe the account trial period, and the documentation does not guarantee that an individual stream can run indefinitely. Ask Castr what happens to an active YouTube broadcast when the account trial expires.
Does the 5 GB trial bandwidth limit apply to YouTube viewers?
Castr describes the 5 GB allowance as bandwidth for embeddable-player use, especially website streaming. Do not translate it into a YouTube audience or runtime cap. If you also embed the stream on your own site, ask how that player usage is counted.
Can a trial account loop content continuously through TV Playout?
Castr’s TV Playout guide says Trial, Starter and Standard do not support Loop mode. That restriction is specific to repeating scheduled media through TV Playout. It should not be applied to a separate live encoder or camera stream without confirmation.
What should I confirm before relying on a continuous trial stream?
Ask Castr in writing about the current trial end date, YouTube destination access, any session-duration restriction, and what happens to an active broadcast at expiry. Describe whether you are using a live input or TV Playout, and test the exact workflow privately before relying on it for an unattended event.