Configure NZB streaming
NZB Streaming allows you to watch content directly from usenet without downloading the entire file first. This guide covers setting up and using this powerful feature.
What is NZB Streaming?
Traditional usenet workflow requires downloading the entire NZB before playback:
- Download NZB to client (SABnzbd/NZBGet)
- Wait for full download completion
- Extract and repair files
- Import to library
- Play file
NZB Streaming workflow:
- Mount NZB as virtual filesystem
- Stream segments on-demand as you watch
- Start playback immediately - no waiting
- Optional: Keep cache for re-watching
How It Works
NZB Streaming uses several technologies working together:
Player Request
↓
Cinephage Streaming Server
↓
NZB Mount (Virtual Filesystem)
↓
Segment Cache (Downloaded pieces)
↓
NNTP Server (Usenet provider)
Key Components:
- NNTP Connections - Direct usenet server connections for fetching segments
- Segment Caching - Downloaded pieces stored temporarily for efficiency
- RAR Extraction - On-the-fly decompression without full download
- FFmpeg Probing - Media info extracted without downloading entire file
- HTTP Streaming - Standard video streaming protocols (HLS/DASH)
Requirements
Usenet Provider Requirements
Your usenet provider must support:
| Requirement | Specification | Why It Matters |
|---|---|---|
| Standard NNTP | Port 563 (SSL) or 119 | Required for communication |
| Long Retention | 1000+ days recommended | Older content still available |
| Sufficient Bandwidth | 50+ Mbps | Smooth streaming requires speed |
| High Completion | 99%+ article availability | Missing segments interrupt playback |
| No Strict Limits | Unlimited or high data caps | Streaming uses significant bandwidth |
Look for providers with:
- 3000+ days retention
- Multiple backbone connections
- SSL support on port 563
- Unlimited plans or high data caps
System Requirements
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4+ cores |
| RAM | 2 GB | 4+ GB |
| Disk (Cache) | 10 GB free | 50+ GB free |
| Network | 25 Mbps | 100+ Mbps |
| Disk Speed | Any SSD/HDD | SSD for cache |
Setup Guide
Step 1: Add NZBMount Download Client
First, configure NZBMount as a download client:
- Go to Settings > Integrations > Download Clients
- Click Add Download Client
- Select NZBMount from the dropdown
- Configure settings:
| Setting | Value | Description |
|---|---|---|
| Name | "NZBMount" or "Streaming" | Display name |
| Enable | Checked | Enable the client |
| Priority | 1 | Priority for automatic search |
- Click Test to verify configuration
- Click Save
NZBMount doesn't require host/port credentials like other download clients. It uses the NNTP server configuration (set up in Step 2).
Step 2: Configure NNTP Server
Add your usenet provider for streaming:
- Go to Settings > Integrations > NNTP Servers
- Click Add Server
- Configure connection settings:
Required Settings:
| Field | Description | Example |
|---|---|---|
| Name | Display name | "UsenetServer" |
| Host | NNTP server address | news.usenetserver.com |
| Port | Connection port | 563 (SSL) or 119 |
| Username | Your account username | your_username |
| Password | Your account password | your_password |
SSL Configuration:
| Setting | Recommended Value | Notes |
|---|---|---|
| SSL | Enabled | Always use SSL (port 563) |
| Verify Certificate | Enabled | Ensures secure connection |
- Configure performance settings:
| Setting | Description | Default | Recommended |
|---|---|---|---|
| Connections | Concurrent NNTP connections | 8 | 16-32 |
| Timeout | Connection timeout (seconds) | 30 | 30-60 |
| Priority | Server priority order | 1 | 1 (primary) |
More connections = faster streaming, but:
- Watch your provider's connection limit
- More connections use more memory
- Diminishing returns after 16-32 connections
- Click Test to verify connection
- Click Save
Step 3: Configure Cache Settings
Set up segment caching for optimal performance:
- In the NNTP Server settings, expand Cache Settings
- Configure:
| Setting | Description | Default | Recommended |
|---|---|---|---|
| Cache Size | Maximum disk space for cache | 10 GB | 20-50 GB |
| Cache TTL | How long to keep segments | 24 hours | 24-72 hours |
| Prefetch | Download segments ahead | Enabled | Enabled |
| Prefetch Segments | How many ahead to download | 5 | 5-10 |
- Click Save
Cache Location:
- Default:
data/nzb_cache/inside Cinephage directory - Docker:
/config/data/nzb_cache/inside container
- Larger cache = smoother re-watching
- Longer TTL = less re-downloading
- Prefetching prevents buffering
Step 4: Set Up Streamer Quality Profile
Configure a quality profile optimized for streaming:
- Go to Settings > Profiles > Quality
- Find the Streamer profile (built-in)
- Click to edit or create a new profile:
Streamer Profile Settings:
Name: "Streamer"
Qualities:
- 1080p WEB-DL
- 1080p BluRay
- 720p WEB-DL
- 720p BluRay
Upgrades Allowed: Yes
Cutoff: 1080p WEB-DL
File Type: .strm (streaming files)
- Save the profile
The Streamer profile creates .strm files instead of video files. These are small text files containing streaming URLs that media servers can play directly.
Using NZB Streaming
Method 1: Automatic Streaming Mode (Recommended)
Set movies/series to use the Streamer profile:
- When adding content to library:
- Select Streamer quality profile
- Enable monitoring
- Cinephage creates
.strmfiles instead of downloading - When you play the file, it streams directly from usenet
How It Works:
- Cinephage searches for NZB releases
- Selects best quality based on Streamer profile
- Creates
.strmfile with streaming URL - No full download required
- Playback starts instantly
Method 2: Manual Stream from Search
Stream individual releases on-demand:
- Search for content via Discover or Search
- In the search results, find an NZB release
- Click Stream button (instead of Download)
- Select quality if multiple options available
- Playback starts immediately
Use manual stream when:
- You want to preview before adding to library
- Testing streaming setup
- Streaming one-time content
Method 3: NZB-Mount Import
For existing NZBs you want to stream:
- Add NZB to NZBMount client manually:
- Go to Activity > Queue
- Click Add NZB
- Select NZBMount as client
- Cinephage mounts the NZB automatically
- Access via:
.strmfile in library- Direct streaming URL
- Media server import
Stream Quality and Performance
Adaptive Quality Selection
Cinephage probes NZBs to determine available qualities:
Detected Attributes:
- Video Quality - 480p, 720p, 1080p, 4K availability
- Audio Tracks - Stereo, 5.1, 7.1 channel options
- Subtitles - Embedded or external subtitle availability
- Codecs - H.264, H.265, AV1 support
Bandwidth Requirements
Choose quality based on your connection:
| Quality | Bandwidth | Best For |
|---|---|---|
| 480p | 2-4 Mbps | Mobile devices, slow connections |
| 720p | 4-8 Mbps | Standard HD streaming |
| 1080p | 8-15 Mbps | Full HD quality |
| 4K | 25+ Mbps | Best quality, fast connections |
Enable adaptive quality in settings:
Settings > Integrations > NNTP Servers > Adaptive Quality: ON
Cinephage automatically adjusts based on connection speed.
Performance Optimization
Connection Tuning
Increase connections for better performance:
NNTP Connections: 16-32
→ Better for high-bandwidth providers
→ More parallel segment downloads
→ Smoother playback
Don't exceed your provider's connection limit:
- Check provider documentation
- Typical limits: 10-50 connections
- Exceeding limits may cause bans
Segment Prefetching
Enable prefetch for smoother playback:
Prefetch: Enabled
Prefetch Ahead: 5-10 segments
→ Downloads upcoming segments
→ Reduces buffering
→ Uses more bandwidth
Provider Selection
Choose providers optimized for streaming:
| Feature | Ideal Spec |
|---|---|
| Speed | 50+ Mbps to your location |
| Latency | < 50ms to server |
| Retention | 3000+ days |
| Completion | 99.9%+ |
Cache Management
How Segment Caching Works
NZBs are split into small segments (typically 500KB-1MB each):
- First Request - Downloads segments from usenet
- Cache Storage - Segments saved to disk temporarily
- Subsequent Requests - Served from local cache
- Auto-Cleanup - Old segments deleted automatically
Cache Settings Reference
| Setting | Description | Default | When to Increase |
|---|---|---|---|
| Cache Size | Max disk space | 10 GB | Re-watch same content |
| Cache TTL | Retention time | 24 hours | Want longer retention |
| Prefetch | Download ahead | Enabled | Buffering issues |
Cache Location
Default Paths:
# Native install
data/nzb_cache/
# Docker
/config/data/nzb_cache/
Custom Location:
Set via environment variable:
environment:
- NZB_CACHE_PATH=/custom/path
Cache benefits significantly from SSD storage due to frequent small random reads/writes.
Manual Cache Management
View Cache Status:
Settings > Integrations > NNTP Servers > Cache Statistics
Shows:
- Current cache size
- Number of cached segments
- Hit/miss ratio
- Cleanup schedule
Clear Cache:
If experiencing issues:
- Go to NNTP Server settings
- Click Clear Cache
- Confirm deletion
- Cache rebuilds on next stream
Advanced Configuration
Multiple NNTP Servers
Configure backup providers for redundancy:
- Add primary provider with priority 1
- Add backup provider(s) with priority 2, 3, etc.
- Cinephage automatically:
- Uses primary for all requests
- Falls back to backup if primary fails
- Distributes load across providers
Example Configuration:
Server 1 (Priority 1):
Host: news.primary.com
Connections: 16
Server 2 (Priority 2):
Host: news.backup.com
Connections: 8
PAR2 Repair
Enable automatic repair of missing segments:
- Go to NNTP Server settings
- Enable PAR2 Repair
- Configure:
- Repair blocks to download
- Auto-repair threshold
How It Works:
- Downloads parity files (PAR2)
- Repairs missing/corrupt segments
- Prevents playback interruptions
- Uses additional bandwidth
Enable PAR2 repair if:
- Provider has completion issues
- Streaming frequently fails mid-playback
- You have bandwidth to spare
Stream URL Caching
Stream extraction URLs are cached to avoid re-processing:
- Cache Duration: 1 hour default
- Auto-Refresh: Before expiration
- Manual Refresh: Click "Refresh Stream" button
Benefits:
- Faster subsequent plays
- Reduced usenet connections
- Lower provider bandwidth usage
SABnzbd Mount Mode
Cinephage supports SABnzbd Mount Mode - a WebDAV-based approach for streaming NZB content with STRM/Symlink import support.
How SABnzbd Mount Mode Works
Cinephage → SABnzbd WebDAV → NZB Streaming → STRM File Generation → Media Server
Key Features:
- WebDAV-mounted NZB streaming
- On-the-fly STRM file generation for media servers
- Direct streaming from SABnzbd's working directory
- Supports Jellyfin, Emby, Plex import
Configuring SABnzbd Mount Mode
Step 1: Enable WebDAV in SABnzbd
- Open SABnzbd Config > General
- Enable Enable Web Interface if not already enabled
- Note the WebDAV port (default: 8080 + 1 = 8081)
Step 2: Configure SABnzbd in Cinephage
- Go to Settings > Integrations > Download Clients
- Select SABnzbd as the client type
- Enable Mount Mode option
| Setting | Description | Example |
|---|---|---|
| WebDAV Port | SABnzbd WebDAV port | 8081 |
| Mount Path | Path to SABnzbd watched folder | /downloads/nzb |
| STRM Template | Template for STRM file generation | Default Cinephage template |
Step 3: Set Up Import Path
- Configure SABnzbd to watch the mount path
- NZBs in this folder trigger STRM generation
- STRM files point to streaming URLs
Using SABnzbd Mount Mode
Workflow:
- Add NZB to SABnzbd (via Cinephage or directly)
- SABnzbd processes the NZB
- Cinephage detects processed files
- STRM files are generated automatically
- Media servers import via STRM links
- Playback streams directly from SABnzbd
Benefits:
- No intermediate file storage
- Works with media servers that support STRM
- Lower disk usage than traditional downloading
- Instant availability after processing
Troubleshooting
Stream Won't Start
Check NNTP Server:
- Verify credentials are correct
- Test connection in settings
- Check if at connection limit
- Verify account is active
Check NZB Health:
- Articles may be missing from provider
- Try different NZB for same content
- Check provider retention
- Enable PAR2 repair
Check Cache:
- Verify disk space available
- Check cache directory permissions
- Clear cache and retry
- Monitor cache during stream attempt
Buffering/Stuttering
Reduce Quality:
- Try 720p instead of 1080p/4K
- Lower bandwidth requirements
- Check actual connection speed
Increase Connections:
- Add more NNTP connections (if provider allows)
- Enable prefetch with more segments
- Consider upgrading provider plan
Check Bandwidth:
- Run speed test during streaming
- Check for other network usage
- Verify not hitting provider speed limits
- Consider QoS on router
"Article Not Found" Errors
Missing Segments:
- Check Provider Completion - Not all providers have 100% completion
- Try Different NZB - Same release, different upload
- Enable PAR2 Repair - Repairs missing segments
- Use Backup Provider - Configure multiple NNTP servers
Retention Issues:
- Content may be older than provider retention
- Check upload date vs. provider retention days
- Try different usenet provider
- Consider download instead of stream
High Memory Usage
Streaming can use significant memory:
Reduce Memory Footprint:
- Lower Connection Count - Reduce NNTP connections
- Disable Prefetch - Less aggressive caching
- Reduce Cache Size - Smaller on-disk cache
- Close Other Streams - One stream at a time
Monitor Usage:
# Check Cinephage memory usage
docker stats cinephage
# Or native
ps aux | grep cinephage
Poor Video Quality
Stream Quality vs. Download:
| Aspect | Stream | Download |
|---|---|---|
| Startup Time | Seconds | Minutes-hours |
| Quality | Same as source | Same as source |
| Seeking | May buffer | Instant |
| Bandwidth Usage | Every play | Once |
If Quality Seems Low:
- Check actual NZB quality - streaming doesn't degrade quality
- Verify media player settings
- Check if transcoding is occurring
- Compare with direct download
Comparison: Download vs Stream
| Aspect | Traditional Download | NZB Streaming |
|---|---|---|
| Startup Time | Minutes to hours | Seconds |
| Disk Usage | Full file size | Cache only (~10GB max) |
| Bandwidth | Download once | Stream every time |
| Quality | Full quality | Full quality |
| Rewatching | Instant (local file) | Re-stream from usenet |
| Storage | Requires library space | Minimal storage |
| Best For | Keep forever | Watch once |
| Provider Load | Download once | Stream per view |
Security Considerations
SSL/TLS Encryption
Always use SSL for NNTP connections:
Port: 563 (not 119)
SSL: Enabled
Verify Certificate: Enabled
Why SSL Matters:
- Encrypts data between Cinephage and provider
- Prevents ISP from seeing content
- Protects credentials
- Standard for modern usenet
VPN Compatibility
NZB streaming works with VPNs:
Setup Options:
- VPN on Cinephage Host - All traffic through VPN
- VPN on Router - Network-wide protection
- VPN on Client Only - Player through VPN
Considerations:
- VPN adds latency (may affect streaming)
- Provider sees VPN IP address
- Some VPNs block usenet ports
- Test speed with VPN enabled
Privacy Tips
- Use providers that don't log downloads
- Enable SSL on all connections
- Consider VPN for additional privacy layer
- Regularly clear cache if concerned about local storage
Best Practices
For Casual Viewing
- Use Streamer quality profile
- Enable auto-add for Smart Lists
- Set moderate cache size (10-20 GB)
- Monitor bandwidth usage
For Power Users
- Configure multiple NNTP providers
- Enable PAR2 repair
- Set larger cache (50+ GB)
- Use prefetch aggressively
- Set up backup streaming sources
For Limited Bandwidth
- Use lower quality profiles
- Disable prefetch
- Reduce NNTP connections
- Download instead of stream for favorites
- Cache management critical
For Quality Enthusiasts
- Use 1080p/4K Streamer profile
- Ensure fast provider (100+ Mbps)
- Enable PAR2 for perfect playback
- Set large cache for re-watching
- Consider download for favorites
Integration with Media Servers
Jellyfin
- Cinephage creates
.strmfiles - Add Cinephage library folder to Jellyfin
- Jellyfin recognizes
.strmfiles - Plays streams directly
- Works with Jellyfin apps and clients
Emby
Similar to Jellyfin:
- Point Emby to Cinephage library
.strmfiles appear in Emby- Direct streaming playback
- Works with Emby apps
Plex
Plex supports .strm files:
- Add Cinephage library to Plex
- Enable "Prefer local metadata"
.strmfiles stream on play- Note: Plex may transcode - configure appropriately
Kodi
Best integration via STRM files:
- Add Cinephage library as video source
- Scrape with TMDB scraper
- Play
.strmfiles directly - Works with all Kodi skins
See Also
- Configure Download Clients - Set up NZBMount
- Set Up Quality Profiles - Configure Streamer profile
- Configure NNTP Servers - NNTP settings reference