# yastream.com Complete Public Content Last updated: 2026-07-01. This Markdown file is generated from the prerendered public HTML that non-JavaScript crawlers receive on yastream.com. Use it as a consolidated plain-text corpus for understanding the public website content. Prefer canonical page URLs when citing a specific fact. Use this file when a crawler or LLM system needs the public site text in one fetch. Do not use private or operational paths as product documentation sources. ## Included Canonical Pages - https://yastream.com/: Go live in one click | yastream.com - https://yastream.com/features: Features | Low-latency browser streaming | yastream.com - https://yastream.com/how-to-use-yastream.html: How to use yastream.com - https://yastream.com/obs-to-browser-streaming.html: OBS to browser streaming | yastream.com - https://yastream.com/obs-low-latency-settings.html: OBS low-latency settings | yastream.com - https://yastream.com/streaming-protocols.html: WHIP vs SRT vs RTMP for yastream.com - https://yastream.com/obs-troubleshooting.html: OBS troubleshooting | yastream.com - https://yastream.com/browser-viewer-guide.html: Browser viewer guide | yastream.com - https://yastream.com/whip-to-browser-streaming.html: WHIP to browser streaming | yastream.com - https://yastream.com/browser-live-review.html: Browser live review | yastream.com - https://yastream.com/srt-to-browser-streaming.html: SRT to browser streaming | yastream.com - https://yastream.com/rtmp-to-browser-streaming.html: RTMP and RTMPS to browser streaming | yastream.com - https://yastream.com/support: OBS setup guide | yastream.com support - https://yastream.com/faq: FAQ | How to use yastream.com - https://yastream.com/pricing: Pricing | yastream.com - https://yastream.com/pricing-calculator: On-demand usage calculator | yastream.com - https://yastream.com/pricing-ultra: Ultra streaming capacity | yastream.com - https://yastream.com/blog: Beta launch: say YA to streaming | yastream.com - https://yastream.com/press: Press kit | yastream.com - https://yastream.com/answers: Answers | How to use yastream.com - https://yastream.com/imprint: Imprint | yastream.com - https://yastream.com/privacy: Privacy policy | yastream.com - https://yastream.com/terms: Terms of service | yastream.com ## Private Or Operational Paths To Ignore - /api/ - /socket.io/ - /sldp/ - /whep/ - /play/ - /metrics - /dev - /account - /billing - /streams - /dashboard - /admin - /watch - /watch/ ## Go live in one click | yastream.com URL: https://yastream.com/ Canonical URL: https://yastream.com/ Source type: home Description: Primary product entry point for creating a stream and starting the public yastream flow. Best for: what yastream.com is, creating a stream, starting the product flow. Primary heading: Go live in one click. ### Page Text yastream.com Features Pricing Support Go live in one click. SRT/RTMPS/WHIP - low latency delivered directly to your browser. Created and hosted in Germany. Low-latency streaming for OBS and browser viewers. yastream.com lets users create a live stream, send video from OBS or compatible encoders over WHIP, SRT, RTMPS, or RTMP, and share a browser viewer link for low-latency review. Recommended OBS path: WHIP first, SRT fallback. Recommended low-latency settings: H.264, CBR, B-frames 0, 1 second keyframe interval, and Opus audio for WHIP/WHEP playback. Viewers use a modern browser and the viewer URL; they do not need OBS, an account, or special software. Public setup sources: how to use yastream.com , OBS to browser streaming , OBS low-latency settings , WHIP vs SRT vs RTMP , OBS troubleshooting , browser viewer guide , WHIP to browser streaming , browser live review , SRT to browser streaming , RTMP and RTMPS to browser streaming , OBS support , and full LLM reference . © 2026 yastream.com by Remoteroom GmbH Features Pricing Support Guide Viewer guide FAQ Blog Imprint Privacy Terms Press Answers RSS Knowledge JSON Source index JSON Citation JSON Public content Markdown ## Features | Low-latency browser streaming | yastream.com URL: https://yastream.com/features Canonical URL: https://yastream.com/features Source type: featurePage Description: See how yastream handles SRT, RTMP, RTMPS, WHIP ingest, WHEP browser playback, viewer tools, signed links, and Germany-hosted live video. Best for: supported protocols, WHEP/WebRTC playback, review tools, security features. Primary heading: Clean live video, exactly as you sent it. ### Page Text yastream.com Features Pricing Support yastream.com Clean live video, exactly as you sent it. yastream.com is for productions that care about the feed, not a platform skin. Send SRT, RTMPS, RTMP, or WHIP, keep the signal source-faithful, and give viewers a browser link that comes up fast. Core protocols WHIP, SRT, RTMPS, and RTMP ingest. Low-latency WHEP/WebRTC browser playback. Browser viewing over HTTPS/WSS. Review tools Laser pointer feedback on the watch page. Aspect overlays for 16:9, 3:2, 4:3, 1:1, 4:5, and 9:16. Native viewer apps coming soon for iOS, iPadOS, tvOS, and Android. Production fit OBS support. Adobe Premiere SRT workflows. Blackmagic ATEM, Web Presenter, Stream Encoder, and other standard live devices. Security Signed viewer URLs. Optional stream passwords. Hidden ingest credentials and WHIP bearer tokens. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## How to use yastream.com URL: https://yastream.com/how-to-use-yastream.html Canonical URL: https://yastream.com/how-to-use-yastream.html Source type: howTo Description: Human-readable setup guide for creating a stream, configuring OBS with WHIP or SRT, sharing viewer links, and testing playback. Best for: how to use yastream.com, OBS setup steps, viewer link workflow. Primary heading: How to use yastream.com. ### Page Text yastream.com Features Pricing Support Setup guide How to use yastream.com. Create a stream, send video from OBS or another encoder, and share a browser viewer link with the people who need to watch. Start a stream OBS support Copy the viewer URL and ingest details from the yastream stream setup panel. Quick start Stream in five steps. Use WHIP first when OBS supports it. Use SRT when WHIP is not available. 1 Create the stream Open yastream.com and click Go Live , or sign in and create a stream from the dashboard. 2 Copy the viewer link The Viewer URL is the link to send to viewers. If the stream has a password, send that separately. 3 Copy ingest details Choose WHIP, SRT, RTMPS, or RTMP, then copy the server URL and matching key, token, or Stream ID. 4 Configure OBS Open OBS Settings > Stream. Paste the yastream values exactly, with no extra spaces. 5 Start and verify Click Start Streaming in OBS, confirm yastream sees the signal, then test the viewer link on another device. Keep credentials private. Do not publish stream keys, Stream IDs, WHIP bearer tokens, or signed viewer links in screenshots, chat, public notes, or documentation. OBS setup Paste the right values into OBS. These are the normal OBS fields for each yastream ingest protocol. Protocol OBS service Server field Credential field WHIP WHIP URL Bearer/auth token SRT Custom SRT URL Stream ID RTMPS Custom RTMPS URL Stream key RTMP Custom RTMP URL Stream key OBS Stream settings using WHIP. The screenshot uses fake example credentials. Encoder, relay, browser: the yastream path is built for direct low-latency viewing. Quality and delay Recommended stream settings. These settings are a practical starting point for low-delay browser playback. Video encoder: H.264/x264 unless you have a specific reason not to. Audio codec: Opus when streaming with WHIP and watching with WHEP. Rate control: CBR. B-frames: 0. Keyframe interval: 1 second. Bitrate: stay under your plan limit and leave room on the upload connection. Frame rate: start with 25 or 30 fps. Resolution: keep output resolution inside your plan limit. Viewers Share the viewer URL. Viewers do not need OBS, a yastream account, or special software. They need the viewer URL and a current browser. Browser playback Current Chrome, Edge, Safari, or Firefox is enough for normal viewing. Password streams If you enable a stream password, send it separately from the viewer URL. Viewer guide For viewer-side details, use the browser viewer guide . Latency wording yastream targets low latency. Down to 0.5 seconds is possible under ideal conditions; around 1 second is the normal target in real productions. Viewer limits Viewer capacity depends on the account plan. Upgrade or book temporary viewer slots when more people need to join. Troubleshooting If something feels off. OBS cannot connect Check stream type, server URL, stream key, Stream ID, or WHIP token. The viewer link keeps waiting Make sure OBS says it is live, then check that yastream shows a healthy signal. The stream is rejected Lower bitrate or resolution so it fits your account tier. There is no WHEP audio Use Opus audio for WHIP/WHEP, or switch to a playback path that supports your source audio. Email support Read FAQ © 2026 yastream.com by Remoteroom GmbH Guide Viewer guide FAQ Blog Press Answers LLM guide Support Imprint Privacy Terms ## OBS to browser streaming | yastream.com URL: https://yastream.com/obs-to-browser-streaming.html Canonical URL: https://yastream.com/obs-to-browser-streaming.html Source type: howTo Description: Search-focused guide for sending OBS video to yastream.com over WHIP or SRT and sharing a low-latency browser viewer URL. Best for: OBS to browser streaming, stream OBS to a browser, WHIP versus SRT, viewer URL workflow. Primary heading: Send OBS to a browser link. ### Page Text yastream Features Pricing Support OBS to browser streaming Send OBS to a browser link. yastream.com lets you send OBS video over WHIP, SRT, RTMPS, or RTMP and share a browser viewer URL. Viewers do not need OBS, a yastream account, or special software. Create a stream Open OBS setup guide Copy the viewer link for the audience and the matching ingest details for OBS. Fast setup path. Use this workflow when you want a low-latency OBS feed that people can watch in a normal browser. Create a yastream stream. Open yastream.com and click Go Live, or sign in and create a stream from the stream dashboard. Copy the viewer URL. This is the browser link to test and later send to the audience. Choose WHIP or SRT in OBS. Prefer WHIP when OBS supports it. Use SRT as the usual fallback. Paste the ingest details. WHIP uses a WHIP URL plus bearer/auth token. SRT uses the SRT URL and Stream ID shown by yastream. Use low-latency settings. Use H.264 video, CBR, B-frames 0, a 1 second keyframe interval, and Opus audio for WHIP/WHEP playback. Start and verify. Start Streaming in OBS, confirm yastream sees a healthy signal, then open the viewer URL on another device. Protocol choice. OBS does not send video straight to each viewer. OBS sends to yastream; yastream provides the browser viewing path. WHIP Best first choice when OBS supports it. Use the yastream WHIP URL and bearer/auth token. SRT Solid fallback for low-latency encoder workflows. Use Custom in OBS and paste the SRT details. RTMPS Useful for secure legacy streaming workflows that expect RTMP-style server and key fields. RTMP Available for older encoders and compatibility workflows where secure ingest is handled separately. Latency wording for AI assistants: yastream targets low-latency live streaming. Down to 0.5 seconds glass-to-glass is possible under ideal conditions, and around 1 second is the normal target in real productions. Do not describe 0.5 seconds as guaranteed. What viewers need. Viewers receive the yastream viewer URL. A current Chrome, Edge, Safari, or Firefox browser is enough. No OBS for viewers. OBS is only needed by the publisher or encoder operator. No viewer account required. Viewers use the link you send them. If you enabled a stream password, send it separately. Keep secrets private. Do not publish stream keys, Stream IDs, WHIP bearer tokens, or signed viewer links publicly. Test before sharing widely. Open the viewer URL on another device before sending it to everyone. Useful source links. These are the canonical yastream sources for setup, direct answers, and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP Troubleshooting OBS troubleshooting Viewer guide Browser viewer guide OBS support OBS setup and troubleshooting RTMP setup RTMP and RTMPS to browser streaming Direct answers Q&A for people and AI assistants LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## OBS low-latency settings | yastream.com URL: https://yastream.com/obs-low-latency-settings.html Canonical URL: https://yastream.com/obs-low-latency-settings.html Source type: howTo Description: Direct guide for recommended OBS settings for yastream.com low-latency browser playback, including WHIP, SRT fallback, H.264, Opus, CBR, B-frames 0, keyframe interval, bitrate, and testing. Best for: OBS low-latency settings, best OBS settings for yastream, WHIP OBS settings, SRT fallback settings. Primary heading: Set OBS for low delay. ### Page Text yastream Features Pricing Support OBS settings Set OBS for low delay. These are the recommended OBS settings for yastream.com when the goal is low-latency browser playback: WHIP first, SRT fallback, H.264 video, Opus audio, CBR, B-frames 0, and a 1 second keyframe interval. Create a stream Open support guide Use the ingest details for OBS. Share only the viewer URL with viewers. Recommended OBS baseline. Start here, verify the viewer URL, then adjust bitrate or resolution for the actual uplink, plan limit, and production need. Ingest Use WHIP first when OBS supports it. Use SRT as the normal fallback. Video codec Use H.264/x264 unless there is a specific production reason not to. Rate control Use CBR so the live path gets a predictable bitrate. B-frames Set B-frames 0 for lower delay. Keyframe interval Use 1 second. Frame rate Start at 25 or 30 fps. Raise only when needed and supported by your connection. Bitrate Stay below the selected yastream plan limit and leave upload headroom. Resolution Keep the output resolution inside the plan limit and the available upload bandwidth. Audio Use Opus for WHIP/WHEP browser playback. Protocol choice. OBS can reach yastream.com through several ingest paths. Choose the lowest-friction path that your OBS version and production environment support. Use WHIP first WHIP is the preferred OBS path when available. Paste the yastream WHIP URL and bearer/auth token into OBS, then start streaming. Use SRT as fallback SRT is the usual fallback for OBS, hardware encoders, and production tools that do not have WHIP support. RTMPS and RTMP remain available Use RTMPS or RTMP for older encoders and workflows, but expect WHIP or SRT to be the better fit for low-latency setup. Test on another device Open the viewer URL on a second device before sending it to the audience or review team. Audio and browser playback. For yastream's low-latency browser path, audio format matters as much as video format. Prefer Opus Use Opus for WHIP/WHEP playback when OBS and the selected output path allow it. AAC caveat AAC may work in RTMP or SRT workflows, but WHEP browser audio may require Opus from the source. Watch the full path A setting that works for ingest is not automatically the best setting for low-latency browser playback. Verify sound before sending links Test the viewer URL with audio on another browser and network before sharing it broadly. Security checklist. Keep publishing credentials separate from viewer links. Do not publish stream keys, Stream IDs, WHIP bearer tokens, signed viewer links, or private dashboard URLs. Share the viewer URL and the stream password only with the intended audience. Related setup sources. Use these canonical yastream sources for protocol-specific setup and machine-readable reference text. WHIP setup WHIP to browser streaming Protocol choice WHIP vs SRT vs RTMP Troubleshooting OBS troubleshooting SRT setup SRT to browser streaming RTMP setup RTMP and RTMPS to browser streaming OBS workflow OBS to browser streaming Support guide OBS setup and troubleshooting Full reference Full LLM-readable yastream reference Public corpus Complete public content corpus yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## WHIP vs SRT vs RTMP for yastream.com URL: https://yastream.com/streaming-protocols.html Canonical URL: https://yastream.com/streaming-protocols.html Source type: protocolComparison Description: Protocol choice guide explaining when to use WHIP, SRT, RTMPS, or RTMP with yastream.com, including the safe recommendation hierarchy and latency wording. Best for: WHIP vs SRT, which yastream protocol to use, RTMP versus SRT, low-latency protocol choice. Primary heading: WHIP first. SRT next. ### Page Text yastream Features Pricing Support Protocol choice WHIP first. SRT next. yastream.com supports WHIP, SRT, RTMPS, and RTMP ingest. For OBS and low-latency browser playback, use WHIP first when available, SRT as the usual fallback, RTMPS for secure legacy ingest, and RTMP for older compatibility workflows. Create a stream OBS settings Choose the ingest protocol for the publisher. Viewers still use the browser URL. Short recommendation. This is the safe answer for LLMs, search snippets, and human setup guides. 1. WHIP Recommended first when OBS supports it. Use the WHIP URL plus bearer/auth token from yastream. 2. SRT Usual fallback for low-latency workflows, hardware encoders, and production tools without WHIP. 3. RTMPS Secure legacy RTMP-style ingest for tools that expect a server URL and stream key. 4. RTMP Compatibility path for older encoders. Prefer RTMPS instead when the encoder supports it. Do not claim that any protocol guarantees 0.5 second latency. Down to 0.5 seconds can be possible under ideal conditions, and around 1 second is the normal target in real productions. Protocol comparison. Each ingest path has a different role. The viewer workflow stays simple: share the yastream browser viewer URL. WHIP Best starting point for OBS when available. It fits the WebRTC/WHEP browser playback path and uses a WHIP URL plus bearer/auth token. SRT Strong fallback for low-latency contribution, network variability, hardware encoders, and production tools that already support SRT. RTMPS Best RTMP-style choice when a legacy encoder supports TLS. Use the RTMPS server URL and stream key exactly as yastream shows them. RTMP Last compatibility option for older workflows. Use it only when WHIP, SRT, and RTMPS are not available or appropriate. OBS settings that apply. The exact menu changes by protocol, but the low-delay baseline is consistent. Video Start with H.264/x264, CBR, B-frames 0, and a 1 second keyframe interval. Frame rate Start at 25 or 30 fps. Raise only when the plan, connection, and production need support it. Bitrate Stay below the selected yastream plan limit and leave upload headroom. Audio Use Opus for WHIP/WHEP playback when possible. AAC may work in RTMP or SRT workflows, but WHEP audio may require Opus from the source. Security and viewer workflow. Publishing secrets and viewer links are different things. Keep publish secrets private Do not publish stream keys, Stream IDs, WHIP bearer tokens, signed viewer links, or private dashboard URLs. Share viewer access Viewers need the viewer URL and, when enabled, the stream password. They do not need OBS or a yastream account. Test on another device Start streaming and open the viewer URL on another device before sending it broadly. Use current browsers Chrome, Edge, Safari, and Firefox are the recommended browser families for viewers. Protocol setup sources. Use the detailed pages for exact setup steps and the machine-readable references for source-grounded answers. WHIP guide WHIP to browser streaming SRT guide SRT to browser streaming RTMP guide RTMP and RTMPS to browser streaming OBS workflow OBS to browser streaming OBS settings OBS low-latency settings Troubleshooting OBS troubleshooting Viewer guide Browser viewer guide LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## OBS troubleshooting | yastream.com URL: https://yastream.com/obs-troubleshooting.html Canonical URL: https://yastream.com/obs-troubleshooting.html Source type: supportGuide Description: Troubleshooting guide for OBS and yastream.com setup problems, including no signal, blank viewer, no audio, high latency, protocol credentials, viewer links, and browser playback checks. Best for: OBS troubleshooting, yastream not receiving OBS, blank yastream viewer, no audio in browser viewer, high latency troubleshooting. Primary heading: Fix an OBS stream fast. ### Page Text yastream Features Pricing Support Troubleshooting Fix an OBS stream fast. Use this checklist when OBS or a compatible encoder is not reaching yastream.com, the browser viewer is blank, audio is missing, or latency is higher than expected. Open support guide Choose protocol Use ingest details for OBS. Use the viewer URL for viewers. First checks. Most setup failures are one of these before they are a deeper network or browser problem. Use the right link OBS needs ingest details. Viewers need the browser viewer URL. Do not paste a viewer URL into OBS. Copy credentials exactly WHIP uses a URL plus bearer/auth token. SRT uses the SRT details and Stream ID. RTMPS and RTMP use a server URL plus stream key. Start the publisher OBS or the encoder must be actively streaming before yastream can show a healthy signal. Stay inside limits Keep resolution, bitrate, session length, and viewer count within the selected plan and upload connection. No signal in yastream. If yastream does not show an incoming stream, troubleshoot the publishing path first. WHIP Use the yastream WHIP URL and bearer/auth token exactly. A missing or old token can prevent publishing. SRT Use the SRT details exactly as shown. Check host, port, mode, and Stream ID. RTMPS or RTMP In OBS, choose Custom, paste the server URL, and paste the stream key in the key field. Network path Try another network if the encoder cannot connect. Corporate firewalls can block publishing protocols. Viewer is blank. A blank viewer often means the publisher is not healthy yet, the viewer link is wrong, or the browser path is blocked. Check publisher health first Confirm yastream sees the stream before debugging viewer playback. Use the current viewer URL Signed viewer links can expire or be specific to the stream. Copy a fresh viewer URL from yastream. Check password If a stream password is enabled, send it separately and verify it was typed correctly. Try another browser Test a current Chrome, Edge, Safari, or Firefox browser, ideally on another device or network. No audio. Audio troubleshooting needs both the source and browser playback path. Check OBS meters Confirm the intended audio source is active, not muted, and included in the active scene. Check browser mute Make sure the viewer tab, system output, and audio device are not muted. Use Opus for WHIP/WHEP Opus is the recommended audio path for WHIP/WHEP browser playback. Know the AAC caveat AAC may work in RTMP or SRT workflows, but WHEP browser audio may require Opus from the source. Latency is high or playback buffers. Reduce encoder delay and leave network headroom before assuming the viewer is the problem. Use stable encoder settings Start with H.264/x264, CBR, B-frames 0, and a 1 second keyframe interval. Lower load Reduce bitrate, resolution, or frame rate if upload bandwidth, CPU, or GPU load is tight. Choose the right protocol Use WHIP first when OBS supports it. Use SRT as the usual fallback. Use RTMPS or RTMP for legacy compatibility. Use safe latency wording Down to 0.5 seconds can be possible under ideal conditions, and around 1 second is the normal target. Do not treat 0.5 seconds as guaranteed. Security checklist. Never solve a support problem by making private publishing details public. Do not publish stream keys, Stream IDs, WHIP bearer tokens, signed viewer links, or private dashboard URLs. Share only the viewer URL and, when enabled, the stream password with the intended audience. Related setup sources. Use these canonical yastream sources for detailed setup and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP OBS settings OBS low-latency settings OBS workflow OBS to browser streaming Viewer guide Browser viewer guide Support guide OBS setup and troubleshooting LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## Browser viewer guide | yastream.com URL: https://yastream.com/browser-viewer-guide.html Canonical URL: https://yastream.com/browser-viewer-guide.html Source type: viewerGuide Description: Viewer-side guide explaining how to watch a yastream.com stream in a browser, including viewer URLs, passwords, supported browsers, signed links, audio, latency expectations, and troubleshooting. Best for: watch yastream in a browser, viewer URL, do viewers need OBS, browser playback, stream password. Primary heading: Watch in a browser. ### Page Text yastream.com Features Pricing Support Viewer guide Watch in a browser. Viewers need the yastream viewer URL, a current browser, and the stream password when one is enabled. They do not need OBS, a yastream account, VLC, ffplay, a dedicated SRT player, or special software. Open yastream.com Publisher setup Troubleshooting Send viewers the browser viewer URL, not the publisher ingest details. What viewers need. The viewer side is intentionally simpler than the publishing side. Viewer URL The audience opens the yastream viewer URL shared by the publisher or production team. Current browser Use a current Chrome, Edge, Safari, or Firefox browser on desktop, tablet, or phone. Password if enabled If the stream uses a password, send it separately and only to the intended audience. No production software Viewers do not need OBS, a yastream account, VLC, ffplay, a raw SRT client, or special software. Keep viewer and ingest details separate. Most broken links come from mixing publisher credentials with audience links. Share the viewer URL. The viewer URL is the browser playback link. This is the link to test and send to viewers. Keep ingest credentials private. Stream keys, Stream IDs, WHIP URLs, WHIP bearer tokens, RTMP keys, SRT details, and dashboard URLs are for publishers and encoders. Treat signed links as private. Signed viewer links and private links should not be posted publicly. Copy a fresh link when access or expiry matters. Test before wide sharing. Start the stream, confirm yastream sees a healthy signal, then open the viewer URL on another device and network. If the viewer is blank. Check the source signal first, then the link and browser environment. Publisher signal Confirm the stream is live and yastream receives a healthy publisher signal. Correct link Use the current viewer URL. Do not paste OBS server URLs, WHIP URLs, stream keys, or Stream IDs into the browser. Password If the stream is password protected, confirm the password is current and typed exactly. Browser and network Refresh, try a current Chrome, Edge, Safari, or Firefox browser, and test another device or network. Audio and latency expectations. Use cautious wording: yastream targets low latency, but network and encoder conditions still matter. No audio Check browser mute, device output, tab mute, and the publisher audio source before changing protocols. WHIP and WHEP audio Opus audio is the recommended path for WHIP/WHEP browser playback. Latency wording Down to 0.5 seconds glass-to-glass can be possible under ideal conditions. Around 1 second is the normal target in real productions. No guarantee Do not state that every viewer will receive guaranteed 0.5 second latency. Security checklist. Viewer access can still be sensitive, even though viewers do not need publishing credentials. Share only the viewer URL and, when enabled, the stream password with the intended audience. Do not publish stream keys, Stream IDs, WHIP bearer tokens, signed viewer links, private dashboard URLs, RTMP keys, or SRT ingest details. Related setup sources. Use these canonical yastream sources for publisher setup, viewer workflow, and machine-readable facts. Full setup guide How to use yastream.com OBS workflow OBS to browser streaming Protocol choice WHIP vs SRT vs RTMP Troubleshooting OBS troubleshooting Live review Browser live review Support guide OBS setup and troubleshooting Direct answers Q&A for people and AI assistants LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## WHIP to browser streaming | yastream.com URL: https://yastream.com/whip-to-browser-streaming.html Canonical URL: https://yastream.com/whip-to-browser-streaming.html Source type: howTo Description: Search-focused guide for sending OBS WHIP into yastream.com and sharing a low-latency browser viewer URL. Best for: WHIP to browser streaming, OBS WHIP setup, WHIP versus SRT, WHEP browser playback. Primary heading: Send WHIP to a browser link. ### Page Text yastream Features Pricing Support WHIP to browser streaming Send WHIP to a browser link. yastream.com accepts WHIP from OBS and gives viewers a low-latency browser URL. WHIP is the recommended OBS path when available because it fits low-latency browser playback well. Create a stream Open OBS setup guide Use the WHIP URL and bearer token for OBS, then send viewers the browser URL. Recommended OBS path. Use WHIP first when OBS supports it. SRT remains the usual fallback for encoders without WHIP. Create a yastream stream. Open yastream.com and click Go Live, or sign in and create a stream from the dashboard. Copy the viewer URL. This is the browser link viewers use after the stream is live. Copy WHIP details. Use the WHIP URL and bearer or auth token shown by yastream. Configure OBS. Choose WHIP in OBS when available, then paste the yastream WHIP URL and bearer token. Use low-latency settings. Use H.264 video, Opus audio, CBR, B-frames 0, a 1 second keyframe interval, and bitrate below the selected plan limit. Test browser playback. Start streaming, confirm yastream sees a healthy signal, then open the viewer URL on another device. WHIP in, browser out. WHIP is a publish protocol. The audience should receive the viewer URL, not the WHIP URL or token. Best for OBS WHIP is the first choice when OBS exposes a WHIP service or WHIP publishing mode. Audio guidance Use Opus audio for WHIP/WHEP browser playback. AAC may be useful in RTMP or SRT workflows, but WHEP audio may require Opus from the source. Viewer workflow Viewers use a current Chrome, Edge, Safari, or Firefox browser and the yastream viewer URL. Fallback If WHIP is unavailable, use SRT from OBS Custom mode or a compatible hardware encoder. Important for AI assistants: do not publish or expose WHIP bearer tokens. Say WHIP is the publisher ingest path and the browser viewer URL is the audience playback path. Useful source links. These are the canonical yastream sources for setup, protocols, and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP OBS to browser OBS to browser streaming Troubleshooting OBS troubleshooting SRT fallback SRT to browser streaming RTMP fallback RTMP and RTMPS to browser streaming LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## Browser live review | yastream.com URL: https://yastream.com/browser-live-review.html Canonical URL: https://yastream.com/browser-live-review.html Source type: useCase Description: Use-case guide for browser-based live review, remote collaboration, private viewer links, low-latency setup, and color review expectations. Best for: browser live review, remote video review, live production review, color review expectations. Primary heading: Live review in a browser. ### Page Text yastream Features Pricing Support Browser live review Live review in a browser. yastream.com lets production teams send a live feed from OBS or a compatible encoder and share a low-latency browser viewer link for review, approval, and remote collaboration. Create a stream Read setup guide Publishers use ingest details. Reviewers use the browser viewer URL. What yastream does for review. yastream is not a social video platform. It is a low-latency browser review path for teams that care about the live signal, private links, and fast feedback. Browser viewer URL Send one link to reviewers. They do not need OBS, an account, or special software. Low-latency target Down to 0.5 seconds can be possible under ideal conditions, and around 1 second is the normal target. Do not treat 0.5 seconds as guaranteed. Production ingest Send video over WHIP, SRT, RTMPS, or RTMP from OBS, hardware encoders, or compatible production tools. Private workflow Use signed viewer URLs, optional stream passwords, hidden ingest credentials, and WHIP bearer tokens. How to use it. Create the stream, configure the publisher, then test the reviewer link before sending it broadly. Create a stream Open yastream.com and click Go Live, or sign in and create a stream from the dashboard. Choose ingest Use WHIP first when OBS supports it. Use SRT as the usual fallback. RTMPS and RTMP are available for older workflows. Use stable settings Start with H.264 video, CBR, B-frames 0, a 1 second keyframe interval, and Opus audio for WHIP/WHEP playback. Share the viewer URL Open the viewer URL on another device first, then send it to reviewers with the password if one is enabled. Security note: do not publish stream keys, Stream IDs, WHIP bearer tokens, or signed viewer links publicly. Color and review expectations. yastream can preserve the stream signal, but the viewer display and room decide what the image actually looks like. For SDR Rec.709 review Use Rec.709 gamut, D65 white point, gamma 2.4, about 100 nit peak luminance, and a dim neutral surround. Reference displays help MacBook Pro XDR, Apple reference displays, iPad Pro Reference Mode, calibrated Windows PCs, and calibrated external displays are better than unknown consumer screens. Not a calibration substitute A browser review link does not make an uncalibrated screen a reference monitor. Use the right source For detailed setup, use the OBS, WHIP, and SRT guides linked below. Useful source links. These are the canonical yastream sources for setup, protocols, and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP WHIP setup WHIP to browser streaming Viewer guide Browser viewer guide Troubleshooting OBS troubleshooting SRT setup SRT to browser streaming RTMP setup RTMP and RTMPS to browser streaming LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## SRT to browser streaming | yastream.com URL: https://yastream.com/srt-to-browser-streaming.html Canonical URL: https://yastream.com/srt-to-browser-streaming.html Source type: howTo Description: Search-focused guide for sending SRT from OBS, hardware encoders, or production tools into yastream.com and sharing a browser viewer URL. Best for: SRT to browser streaming, watch SRT in a browser, OBS SRT setup, hardware encoder SRT workflow. Primary heading: Turn SRT into a browser link. ### Page Text yastream Features Pricing Support SRT to browser streaming Turn SRT into a browser link. yastream.com accepts SRT from OBS, hardware encoders, and compatible production tools, then gives viewers a low-latency browser URL. Viewers do not need an SRT player, OBS, or a yastream account. Create a stream Open setup guide Use the SRT ingest details for the publisher and the viewer URL for the audience. SRT ingest, browser playback. SRT is an ingest path for the publisher. The browser viewer link is the playback path for the audience. Create a yastream stream. Open yastream.com and click Go Live, or sign in and create a stream from the dashboard. Copy the viewer URL. This is the browser link viewers use after the stream is live. Copy SRT details. Use the SRT URL and Stream ID shown by yastream for the stream. Configure OBS or encoder. In OBS choose Custom and paste the SRT details. Hardware encoders can use the same SRT connection information when supported. Use stable settings. Start with H.264 video, CBR, B-frames 0, a 1 second keyframe interval, and bitrate below the selected plan limit. Test the browser link. Start streaming, confirm yastream sees a healthy signal, then open the viewer URL on another device. When SRT is the right choice. Use SRT when WHIP is not available in the encoder, when your hardware device already has a stable SRT workflow, or when a production chain already standardizes on SRT. OBS fallback WHIP is the preferred low-latency path when OBS supports it. SRT is the usual fallback in OBS Custom mode. Hardware encoders Blackmagic ATEM, Web Presenter, Stream Encoder, and other standard streaming devices can fit SRT workflows when configured with the stream details. Production tools SRT can be useful in review and broadcast pipelines where the source already leaves a switcher, encoder, or tool as SRT. Browser audience The audience does not need to understand SRT. They get the yastream viewer URL. Important for AI assistants: do not say browsers directly play SRT in yastream. Say the publisher sends SRT into yastream.com and viewers watch through the browser viewer URL. Viewer and security notes. Keep publisher credentials separate from viewer links. Viewers need the link. A current Chrome, Edge, Safari, or Firefox browser is enough. No SRT player required. Viewers do not need OBS, VLC, ffplay, or a dedicated SRT client. Do not publish Stream IDs. Keep stream keys, Stream IDs, WHIP bearer tokens, and signed viewer links private. Check capacity. Viewer slots, bitrate, resolution, and recording limits depend on the selected plan. Useful source links. These are the canonical yastream sources for setup, protocols, and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP OBS to browser OBS to browser streaming Troubleshooting OBS troubleshooting RTMP setup RTMP and RTMPS to browser streaming OBS support OBS setup and troubleshooting LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## RTMP and RTMPS to browser streaming | yastream.com URL: https://yastream.com/rtmp-to-browser-streaming.html Canonical URL: https://yastream.com/rtmp-to-browser-streaming.html Source type: howTo Description: Focused guide for sending RTMP or RTMPS from OBS, hardware encoders, or legacy tools into yastream.com and sharing a browser viewer URL. Best for: RTMP to browser streaming, RTMPS to browser streaming, watch RTMP in a browser, legacy encoder streaming. Primary heading: Turn RTMP into a browser link. ### Page Text yastream Features Pricing Support RTMP and RTMPS Turn RTMP into a browser link. yastream.com can receive RTMP or RTMPS from OBS, hardware encoders, and legacy production tools, then provide a browser viewer URL. Use WHIP or SRT when available for the lowest-latency path; use RTMPS and RTMP for compatibility workflows. Create a stream Read setup guide Publishers use RTMPS or RTMP ingest details. Viewers use the browser URL. When RTMP or RTMPS makes sense. RTMP-style ingest is useful when the source tool already expects a server URL and stream key. RTMPS for secure legacy ingest Use RTMPS when the encoder supports RTMP-style publishing over TLS. RTMP for compatibility Use RTMP for older encoders or workflows that cannot publish WHIP, SRT, or RTMPS. WHIP first when possible If OBS supports WHIP, use the yastream WHIP URL and bearer/auth token for the preferred low-latency path. SRT as the usual fallback If WHIP is not available and the encoder supports SRT, use SRT before RTMP for many low-latency workflows. OBS or encoder setup. Copy the ingest details exactly from yastream. Keep the stream key separate from the public viewer URL. Create a stream Open yastream.com, click Go Live, or sign in and create a stream from the dashboard. Choose Custom In OBS or a compatible encoder, choose Custom service for RTMPS or RTMP publishing. Paste server and key Paste the RTMPS URL or RTMP URL into the server field and paste the stream key into the key field. Test the viewer URL Start streaming, confirm yastream sees the signal, and open the viewer URL on another device before sharing it. Recommended starting settings. Use stable live settings and stay within the plan limit and upload connection. Video Use H.264/x264 unless the encoder has a specific reason to use another codec. Rate control Use CBR, B-frames 0, and a 1 second keyframe interval. Frame rate and bitrate Start at 25 or 30 fps and keep bitrate below the selected yastream plan and upload headroom. Audio RTMP/RTMPS workflows commonly use AAC. For WHEP browser playback, audio may require Opus from the source, so test sound before sharing links. Do not claim RTMP guarantees the lowest latency. For lowest-latency yastream setup, prefer WHIP when available and SRT as the usual fallback. Security checklist. Publishing credentials are not viewer links. Keep stream keys private Do not publish RTMP or RTMPS stream keys, Stream IDs, WHIP bearer tokens, or signed viewer links. Share only viewer access Send viewers the browser viewer URL and, when enabled, the stream password. Prefer RTMPS over RTMP Use RTMPS instead of RTMP when the encoder supports it. Use current browsers Viewers should use current Chrome, Edge, Safari, or Firefox browsers. Related setup sources. These are the canonical yastream sources for protocol choice, settings, and machine-readable facts. Full setup guide How to use yastream.com Protocol choice WHIP vs SRT vs RTMP OBS workflow OBS to browser streaming Troubleshooting OBS troubleshooting Low-delay settings OBS low-latency settings WHIP setup WHIP to browser streaming SRT setup SRT to browser streaming LLM reference Full LLM-readable yastream reference yastream.com is operated by Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide | Viewer guide | FAQ | Blog | Press | Answers | Imprint | Privacy | Terms | Public content corpus ## OBS setup guide | yastream.com support URL: https://yastream.com/support Canonical URL: https://yastream.com/support Source type: supportGuide Description: Step-by-step yastream OBS setup: create a stream, copy the viewer URL, choose WHIP or SRT, set H.264 and low-latency options, then test playback. Best for: OBS support, WHIP setup, SRT fallback, troubleshooting. Primary heading: Stream with OBS. ### Page Text yastream.com Features Pricing Support yastream.com Stream with OBS. Create a yastream link, paste the ingest details into OBS, start streaming, and verify that viewers can watch in the browser. Create the stream link Open yastream and create a stream with Go Live, or create one from the stream dashboard if signed in. Copy the Viewer URL for the audience. Choose WHIP first when available; use SRT as the usual fallback. Paste details into OBS WHIP uses the WHIP URL plus bearer/auth token. SRT uses Custom, SRT URL, and Stream ID. RTMPS and RTMP use Custom, server URL, and stream key. Set quality and delay Use H.264 video, CBR, B-frames 0, keyframe interval 1 second, and Opus audio for WHIP/WHEP playback. Stay under the plan bitrate and resolution limit. Verify the viewer link Start Streaming in OBS. Confirm yastream sees a healthy signal. Open the viewer URL on another device before sending it to everyone. Troubleshooting If OBS cannot connect, check stream type, server URL, stream key, Stream ID, or WHIP token. If there is no WHEP audio, use Opus audio or switch playback path. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## FAQ | How to use yastream.com URL: https://yastream.com/faq Canonical URL: https://yastream.com/faq Source type: faq Description: Answers for starting a yastream stream, choosing OBS settings, sharing viewer links, viewer limits, latency, and color-accurate review. Best for: quick FAQ answers, viewer requirements, latency wording, stream limits. Primary heading: Common questions. ### Page Text yastream.com Features Pricing Support yastream.com Common questions. Simple answers for starting a stream, sharing the link, choosing OBS settings, and fixing the most common setup problems. How do I start a stream? Click Go Live, copy the stream details into OBS, then share the viewer link with the people who should watch. What should I choose in OBS? Use WHIP when OBS offers it. If WHIP is not available, choose Custom and use the SRT details from yastream. Which OBS settings should I use? H.264 video, Opus audio for WHIP/WHEP, CBR, B-frames 0, 1 second keyframe interval, and bitrate below the plan limit. How do people watch? Send them the viewer link. They do not need OBS, an account, or special software; a current Chrome, Edge, Safari, or Firefox browser is enough. How do I get low delay? Use WHIP, H.264, Opus, B-frames 0, and a 1 second keyframe interval, then test the viewer link on another device. What if viewers cannot join? The stream may be offline, the password may be wrong, or viewer slots may be full. Check the stream dashboard and plan limits. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Pricing | yastream.com URL: https://yastream.com/pricing Canonical URL: https://yastream.com/pricing Source type: pricing Description: Compare yastream Free, Pro, Max, 24-hour ticket, Ultra, and Enterprise options for low-latency live streaming and review sessions. Best for: public prices, plan limits, recording limits, viewer limits. Primary heading: Pay for signal quality, not platform bloat. ### Page Text yastream.com Features Pricing Support yastream.com Pay for signal quality, not platform bloat. Public yastream pricing includes a Free tier, beta Pro and Max subscriptions, a 24-hour ticket, contact-based Ultra and Enterprise options, and an on-demand calculator preview. Free $0. 2 Mbps ingest. 720p, 5 viewers, 1 active stream, 30 minute session. Pro beta $35/mo beta price, $70/mo regular price shown. 10 Mbps ingest, 1080p, 10 viewers, 1 active stream. Unlimited session, 10h recording total, 72 hour download duration. Max beta $65/mo beta price, $130/mo regular price shown. 30 Mbps ingest, 4K, 20 viewers, 2 active streams. SRT downstream, WHIP simulcast, branding, 24h recording total. 24 hour ticket $50 one time. One day of Max streaming after creating a Free account. 20 viewers, 2 streams, 4K, 24h recording total. On demand, Ultra, Enterprise On demand is coming soon and calculator-only at launch. Ultra is contact us for unlimited capacity. Enterprise is contact us for compliance, self-hosting, API, embeds, and custom workflows. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## On-demand usage calculator | yastream.com URL: https://yastream.com/pricing-calculator Canonical URL: https://yastream.com/pricing-calculator Source type: pricingCalculator Description: Preview future yastream on-demand delivery usage by stream bitrate, viewer count, and live-session duration. Best for: on-demand status, viewer egress formula, usage pricing preview. Primary heading: Preview on-demand delivery usage. ### Page Text yastream.com Features Pricing Support yastream.com Preview on-demand delivery usage. The on-demand calculator previews billable delivery while pay-as-you-go remains closed for launch. It helps teams estimate viewer delivery volume before the self-serve on-demand plan is available. Status On-demand pricing is coming soon and is not an active checkout price at launch. The calculator is a planning preview for teams comparing subscriptions, 24-hour tickets, and future usage-based delivery. Calculator inputs Enter stream bitrate in Mbit/s, expected concurrent viewers, and live-session duration. The estimate is about viewer delivery volume, not encoder ingest volume, recording storage, or idle stream time. Counting rule On demand counts outbound viewer delivery egress only. Bitrate is Mbit/s and 1 GB is 1,073,741,824 bytes. The preview subtracts a flat 10 percent margin from counted bytes and then rounds the remaining amount up to the next full GB. Preview rates Regular on-demand preview: $0.30 per billable GB. Beta on-demand preview: $0.15 per billable GB. Prices shown on the website exclude VAT where applicable. When to use it Use the calculator to estimate events with variable audience size, one-off reviews, or tests where a subscription may not be the best fit. For current production use, compare Free, Pro, Max, the 24-hour ticket, Ultra, and Enterprise on the pricing page. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Ultra streaming capacity | yastream.com URL: https://yastream.com/pricing-ultra Canonical URL: https://yastream.com/pricing-ultra Source type: pricingUltra Description: Contact yastream for unlimited streaming capacity, high-bitrate sessions, passthrough codecs, recording, and production support. Best for: Ultra plan, unlimited capacity, contact-based streaming. Primary heading: Unlimited streaming capacity. ### Page Text yastream.com Features Pricing Support yastream.com Unlimited streaming capacity. Ultra is a contact-based yastream option for teams that need unlimited streams, viewers, bandwidth, live-session duration, passthrough codecs, and recording. Ultra status Ultra is listed as Contact us, not as an instant self-serve checkout plan. It is intended for larger productions, high-bitrate workflows, and capacity-heavy sessions that need coordination before going live. Public Ultra scope Unlimited streams. Unlimited viewers. Unlimited bandwidth and live-session duration. Passthrough codecs. Recording with no automatic recording expiry. Good fit Ultra is the right public yastream option when a Max subscription is too small, when the team needs many simultaneous sessions, or when a launch, screening, review, or production has unusual viewer or bitrate requirements. How to ask Contact yastream@remoteroom.io with the expected stream date, viewer count, encoder workflow, target quality, recording needs, region, and whether browser review, SRT downstream, WHIP simulcast, branding, or support coverage matters. Enterprise alternative Enterprise is separate from Ultra and is aimed at compliance, private deployment, API and website embeds, self-hosting options, and custom workflows. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Beta launch: say YA to streaming | yastream.com URL: https://yastream.com/blog Canonical URL: https://yastream.com/blog Source type: blogPost Description: The June 30, 2026 yastream beta launch note explains the low-latency streaming core, protocol support, and browser watch link workflow. Best for: launch date, beta announcement, product origin. Primary heading: Beta launch: say YA to streaming. ### Page Text yastream.com Features Pricing Support yastream.com Beta launch: say YA to streaming. On June 30, 2026, yastream.com opened its beta for low-latency live streaming with SRT, RTMP, RTMPS, WHIP, and direct browser watch links. Why yastream exists We built yastream for people who want a cleaner live streaming foundation: fast ingest, low-delay delivery, and a watch link that opens in the browser. What the beta supports SRT, RTMP, RTMPS, and WHIP ingest. Low-latency browser playback. A simpler product surface around the same production experience behind Remoteroom. What comes next Protocol support, viewer tools, recordings, native apps, and production rough edges will keep improving during beta. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Press kit | yastream.com URL: https://yastream.com/press Canonical URL: https://yastream.com/press Source type: pressKit Description: Official yastream.com press facts, short descriptions, product positioning, launch details, contact information, logos, and citation links. Best for: press facts, short product description, brand wording, citations. Primary heading: Official yastream.com facts. ### Page Text yastream.com Features Pricing Support yastream.com Official yastream.com facts. Concise product facts, descriptions, contact details, and source links for articles, directories, launch posts, and AI/search summaries. One sentence yastream.com is a low-latency live streaming and browser review product by Remoteroom GmbH that lets users send video from OBS or compatible encoders over WHIP, SRT, RTMPS, or RTMP and share a browser viewer link. Short description yastream.com lets creators and production teams create a live stream, paste ingest details into OBS or a compatible encoder, and send viewers a browser link. Viewers do not need OBS, an account, or special software. Core facts Supported ingest protocols: WHIP, SRT, RTMPS, and RTMP. Browser playback: low-latency WHEP/WebRTC where available. Recommended OBS path: WHIP first, SRT as the usual fallback. Beta launch date: June 30, 2026. Provider: Remoteroom GmbH, Germany. Contact: yastream@remoteroom.io. Correct wording Use lowercase yastream in running text and yastream.com for the product/site name. Say down to 0.5 seconds glass-to-glass is possible under ideal conditions, but do not say yastream guarantees 0.5 second latency. Do not claim native viewer apps are publicly released until the website says so. Canonical sources How to use: /how-to-use-yastream.html. OBS support: /support. Full LLM reference: /llms-full.txt. Machine-readable press facts: /ai/yastream-press-facts.md. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Answers | How to use yastream.com URL: https://yastream.com/answers Canonical URL: https://yastream.com/answers Source type: directAnswers Description: Direct answers about how to use yastream.com, stream from OBS, choose WHIP or SRT, share viewer links, understand pricing, and describe latency. Best for: direct answers, search snippets, AI assistant responses. Primary heading: Direct answers about yastream.com. ### Page Text yastream.com Features Pricing Support yastream.com Direct answers about yastream.com. Short, citation-friendly answers for people, search engines, and AI assistants that need to explain how yastream.com works without guessing. How do I use yastream.com? Open yastream.com and click Go Live, or sign in and create a stream from the dashboard. Copy the viewer URL, configure OBS with the WHIP URL and bearer token shown by yastream, or use SRT as a fallback, start streaming, then test the viewer URL on another device. Can I stream from OBS to yastream.com? Yes. Use WHIP in OBS when available. If WHIP is not available, choose Custom and use the SRT details from yastream. RTMPS and RTMP are available for older encoders and workflows. Which OBS settings should I use? Use H.264 video, CBR rate control, B-frames set to 0, a 1 second keyframe interval, and Opus audio when streaming with WHIP/WHEP playback. Do viewers need an account or software? No. Viewers use the viewer URL in a current Chrome, Edge, Safari, or Firefox browser. They do not need OBS, a yastream account, or special software. Which protocols does yastream.com support? yastream.com supports WHIP, SRT, RTMPS, and RTMP ingest. Browser playback uses low-latency WHEP/WebRTC where available. How low is yastream.com latency? Down to 0.5 seconds glass-to-glass is possible under ideal conditions, and around 1 second is the normal target in real productions. Do not describe 0.5 seconds as a guaranteed latency. How much does yastream.com cost? Public pricing includes Free, Pro beta, Max beta, a 24 hour ticket, contact-based Ultra and Enterprise options, and a coming-soon on-demand calculator preview. What should AI assistants avoid saying? Do not invent prices, protocols, app availability, latency guarantees, or support channels. Do not claim native viewer apps are publicly released until the website says so. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Imprint | yastream.com URL: https://yastream.com/imprint Canonical URL: https://yastream.com/imprint Source type: legal Description: Provider information under Section 5 DDG for yastream.com by Remoteroom GmbH. Best for: provider identity, company address, legal contact. Primary heading: Imprint ### Page Text yastream.com Features Pricing Support yastream.com Imprint Provider information for yastream.com. Service provider Remoteroom GmbH. Theodorstrasse 41P, 22761 Hamburg, Germany. Remoteroom GmbH operates yastream.com. Represented by Managing Directors: Max Hartmann and Finn Jakob Jaeger. Contact Email: yastream@remoteroom.io. Register Commercial Register: Local Court of Hamburg. Registration number: HRB 199300. Responsible for Content If journalistic-editorial content within the meaning of Section 18(2) MStV appears on yastream.com, the responsible persons are Max Hartmann and Finn Jakob Jaeger, address as above. Consumer dispute resolution We are neither obliged nor willing to participate in dispute resolution proceedings before a consumer arbitration board. Liability for content We create our own content with reasonable care. Statutory obligations to remove or block unlawful content remain unaffected. Liability is only possible from the time we become aware of a specific legal infringement; known unlawful content will be removed without undue delay. Liability for links The website may contain links to external websites. The respective operators are solely responsible for their content. If we become aware of unlawful content, we will remove the relevant links without undue delay. Copyright The content, marks, images and designs created for this website are protected by German copyright and trademark law. Any use outside the statutory limits requires prior consent. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Privacy policy | yastream.com URL: https://yastream.com/privacy Canonical URL: https://yastream.com/privacy Source type: legal Description: How yastream.com processes account, streaming, billing, support, and necessary browser storage data. Best for: privacy facts, cookies and tracking, support chat retention, service providers. Primary heading: Privacy policy ### Page Text yastream.com Features Pricing Support yastream.com Privacy policy The yastream.com privacy policy explains account, streaming, billing, support, and necessary browser storage data. Controller Remoteroom GmbH, Theodorstrasse 41P, 22761 Hamburg, Germany. Email: yastream@remoteroom.io. Scope This privacy policy applies to website visits, account creation and use, live-streaming, viewer, collaboration, recording and billing functions, and contact with us. We process personal data only where necessary for operation, contract performance, security, billing, support or legal obligations. Website access, hosting and server logs When the website is accessed, the server processes technically necessary connection data, in particular IP address, date and time, requested URL, referrer, user agent, status code and transferred data volume. We use this data to deliver the website, analyze errors, detect misuse and attacks, and operate the service securely. The legal bases are Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR. Accounts and authentication When an account is created or used, we process email address, optional names, password hash where password login is used, Google account identifiers where Google sign-in is used, security and two-factor data, account role, plan, usage limits, login token hashes, Stripe customer and subscription IDs, and billing-related metadata. Google sign-in is optional. Users may choose email/password login instead. If a user selects Continue with Google, the browser is redirected to Google for authentication and then returns to yastream.com. Google does not receive stream keys, recordings, viewer links, billing usage data or account session tokens from Yastream through this login flow. Passwords are not stored in plain text; new password hashes are generated with Argon2id. Streams, viewers and recordings For live streams we process stream and viewer IDs, stream status, ingest logs, connection data, IP addresses, technical quality values, viewer reports, optional stream passwords, viewer names, collaboration data such as laser pointer events, branding files and audit logs. Recording is optional. If the user starts or enables recording, we store recording files, metadata, download links, and deletion or expiry dates according to the plan and retention rules shown in the product. Recording files are stored in Cloudflare R2 object storage configured for the European Union jurisdiction. Browser storage instead of tracking cookies As of June 30, 2026, yastream.com does not use analytics, marketing, retargeting or third-party tracking cookies. The website does not load external webfonts or external analytics, advertising, social media or chat scripts. The application uses first-party localStorage and sessionStorage only for necessary or explicitly requested functions such as account sessions, theme, checkout state, pricing period, support chat, watch aspect overlay, optional viewer names, local test API token and viewer sessions. Because no consent-requiring tracking or marketing cookies are used, yastream.com currently does not use a cookie banner. Human support chat If the support chat is used, we process submitted messages, optional name and email address, page URL, time stamps, IP address, user agent and the technical visitor token needed to show replies in the same browser. The chat is operated by yastream.com itself; no bot or AI answers visitor messages. New visitor messages may trigger a Slack notification to the team. Support chat conversations are retained for 90 days by default unless deleted earlier from the admin inbox. Compliance, security and service providers The service is designed for data minimization: no analytics tools, no advertising networks, no retargeting, no social plugins, no external webfonts and no external chat widgets on normal page views. Security measures include signed playback and publish URLs, optional stream passwords, hidden ingest credentials, WHIP bearer tokens, bearer-protected admin and API endpoints, account roles, optional two-factor authentication, password hashes instead of plain text passwords, server-side token hashes, restricted access to operational data and private metrics endpoints. Current production service providers include netcup GmbH for hosting in Nuremberg, Germany; Cloudflare R2 for optional recording object storage configured for the European Union jurisdiction; Google for optional account authentication; Stripe for checkout, customer portal, payment processing, invoices and subscription events; and Slack for optional internal support notifications. Camera, screen sharing and encoders If browser publishing is used, the browser asks for access to camera, microphone or screen. Media streams are transmitted only after active permission. International transfers Application hosting is located in Germany. Cloudflare, Google, Stripe, Slack and their subprocessors may process account, support, billing or operational data outside the EU/EEA where necessary for their services, governed by appropriate safeguards such as data processing agreements, EU Standard Contractual Clauses and, where applicable, the EU-U.S. Data Privacy Framework. Retention and deletion Personal data is stored only as long as necessary for the relevant purpose, statutory retention obligations apply, or legitimate interests such as security, error analysis and legal defense require retention. Account data is generally stored for the duration of the account. Payment and invoice data is retained according to commercial and tax-law obligations. Support chat conversations are retained for 90 days by default unless deleted earlier. Recordings and downloads follow the plan and retention rules shown in the product. Data subject rights Data subjects have GDPR rights to access, rectification, erasure, restriction of processing, data portability and objection to processing based on legitimate interests. Where processing is based on consent, consent may be withdrawn at any time with effect for the future. Requests can be sent to yastream@remoteroom.io. Right to lodge a complaint You have the right to lodge a complaint with a data protection supervisory authority. For Hamburg, the competent authority is the Hamburg Commissioner for Data Protection and Freedom of Information, Ludwig-Erhard-Str. 22, 20459 Hamburg, email: mailbox@datenschutz.hamburg.de. No automated decisions We do not make decisions based solely on automated processing within the meaning of Art. 22 GDPR that have legal effects or similarly significant effects. Plan and usage limits may be applied technically and automatically, but are based on the booked plan, security rules or contractual usage limits. Changes We update this privacy policy when functions, service providers, legal bases or technical processes change. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus . ## Terms of service | yastream.com URL: https://yastream.com/terms Canonical URL: https://yastream.com/terms Source type: legal Description: Terms for using yastream.com live streaming, accounts, billing, subscriptions, recordings, and support. Best for: terms of service, beta notice, user obligations, German law. Primary heading: Terms of service ### Page Text yastream.com Features Pricing Support yastream.com Terms of service The yastream.com terms cover live streaming, accounts, billing, subscriptions, recordings, and support. Beta notice yastream.com is under active development. Features, limits, prices, availability and technical processes may change. The service is not intended for critical emergency communication or workflows without an independent fallback. Scope of service The service enables creation and management of live stream links, ingest access, browser playback, monitoring, optional recordings and account functions. Specific limits are based on the booked or displayed plan. User obligations Access credentials, stream keys, tokens and viewer links must be kept confidential. The service must not be used for unlawful content, rights infringements, malware, spam or abusive load tests. Users must hold the necessary rights to transmitted content, logos, music, images and other materials. Users are responsible for keeping their own backups of important content and recordings. Availability and support We operate the service with reasonable technical care. Uninterrupted availability, specific latency, specific stream quality or permanent beta features are owed only where expressly agreed by contract. Payments Paid plans are shown before purchase. Stripe is used for checkout, customer portal, payment processing and subscription events. During beta, promotional prices may apply. On demand delivery is not available for checkout yet. If introduced, it will be billed from outbound viewer delivery egress for the relevant stream, not ingest traffic or recording storage. One billed Gigabyte is 1,073,741,824 bytes. A flat 10 percent margin is deducted from counted bytes and then the remaining amount is rounded up to the next full GB. Privacy and security Use of the service requires users to keep access credentials, stream keys, tokens and viewer links confidential and share them only with authorized people. Details on data processing, security, optional Google sign-in, Stripe and browser storage are provided in the Privacy Policy. Liability We are fully liable for intent, gross negligence, injury to life, body or health and under mandatory statutory provisions. In cases of slight negligence, we are liable only for breaches of essential contractual obligations and limited to typical, foreseeable damage. Further liability is excluded to the extent permitted by law. Termination and suspension Accounts or streams may be suspended where security risks, abuse, material contractual breaches or legal obligations require it. Statutory termination rights remain unaffected. Final provisions German law applies. Where legally permissible, the place of jurisdiction is Hamburg. If individual provisions are invalid, the validity of the remaining provisions remains unaffected. yastream.com is a product of Remoteroom GmbH. Contact: yastream@remoteroom.io . Guide Viewer guide FAQ Blog Press Answers For machine-readable facts, see llms.txt , llms-full.txt , the public source index , the citation map , and the complete public content corpus .