AIOStreams: Complete Setup and Configuration Guide (2026)
AIOStreams is an aggregator framework. It does not host content itself. You are responsible for legal source usage and service terms in your jurisdiction.
What AIOStreams Actually Does
AIOStreams is a Stremio super-addon that:
- Collects results from multiple addons.
- Applies one shared filter/sort/dedup pipeline.
- Outputs one normalized stream list.
This means you stop tuning every individual addon and tune one central engine instead.
Before You Configure
You need:
- A running AIOStreams instance (
/stremio/configureURL). - At least one stream provider addon.
- Any service credentials you plan to use (Debrid, TorBox, etc.).
- Optional TMDB access token for title-matching filters.
On the public ElfHosted instance, Torrentio is intentionally disabled. Community guides explain wrapping workflows, but availability/rules can change by instance.
Setup Flow (Recommended)
High-Level Setup
- Open your AIOStreams
configurepage. - Configure
Servicesfirst. - Add addons from
Marketplace(orCustom Addon). - Configure
FiltersandSorting. - Configure
Formatter. - Save user configuration and install.
- Test with one title, then iterate.
Menu-by-Menu Configuration Reference
1) Services
Purpose:
- Stores credentials (Debrid and other service integrations).
- Defines service priority order.
How ordering works:
- Service order is used by deduplication and service-based sorting.
- Higher-ranked services win tie-breaks more often.
Common options:
- Debrid service API keys/tokens.
- RPDB API key field (for supported catalog posters).
- Optional TMDB token usage (via matching filters).
Practical rule:
- Put your most reliable service first.
2) Addons
Purpose:
- Add/remove/enable/disable wrapped addons.
- Control addon-level behavior.
Install sources:
Marketplace: curated convenience entries.Custom Addon: any manifest URL.
Important per-addon options (commonly exposed):
Name: Display label in stream results.Timeout: Max wait before addon response is abandoned.Resources: Override which resources are used (stream,catalog, etc.).URL/Override URL: Force a custom manifest/config URL.
Critical caveat:
- If you override addon URLs manually, automatic service credential propagation may not apply to that addon.
Catalog controls under Addons
In the installed catalog manager, you can usually:
- Refresh discovered catalogs.
- Reorder catalogs.
- Rename catalog name/type.
- Move catalogs quickly to top/bottom.
- Toggle visibility.
Use case:
- Keep high-value catalogs in Home, push noisy catalogs to Discover only.
3) Filters
This is the core quality-control layer.
3.1 Cache filter
You can separately control cached and uncached streams:
- Disable cached streams.
- Disable uncached streams.
- Exclude by addon/service/stream type.
- Choose apply mode:
OR: match any excluded dimension.AND: match all excluded dimensions.
3.2 Media attribute filters
Usually includes:
- Resolution
- Encode
- Stream Type
- Visual Tag
- Audio Tag
- Audio Channel
- Language
Most share the same logic buckets:
Required: stream must match at least one.Excluded: stream is dropped if matches.Included: stream bypasses other exclude/required blocks.Preferred: ranking signal used during sorting.
3.3 Seeder filter
RequiredrangeExcludedrangeIncludedrange- Optional stream-type scoping
Good practice:
- Apply seeder filters mainly to P2P streams.
3.4 Matching filters
Title Matching
- Compares stream titles against requested content title.
- Modes:
ExactPartial/contains-style match
- Requires TMDB access token for best results.
- Can be scoped to selected addons or request types.
Season/Episode Matching
- Same intent for episodic disambiguation.
- Helps drop mislabeled episode packs.
3.5 Keyword filter
Buckets:
- Required
- Excluded
- Included
- Preferred (ranking boost when sorting by keyword)
Keywords are typically case-insensitive.
3.6 Regex filter
Power-user version of keyword filtering.
- Required / Excluded / Included / Preferred logic.
- Preferred regex ordering matters (top patterns rank higher).
Instance access controls may restrict regex on public deployments unless trusted UUID rules are met.
3.7 Size filter
- Global min/max size for movies and series.
- Optional per-resolution overrides.
- Resolution-specific limits usually take precedence over global limits.
3.8 Result limits
Hard caps can be applied globally and per group, e.g.:
- Per service
- Per addon
- Per resolution
- Per quality
- Per indexer/release group
This trims tail noise after sorting.
3.9 Deduplicator
Detection methods:
filename(fuzzy normalized filename)infoHash(most precise for torrent-identifiable items)smartDetect(hash from metadata attributes)
Duplicate handling strategies (per stream class):
Single ResultPer ServicePer Addon
Recommended baseline:
- Enable deduplicator.
- Use
Single Resultfor cached/uncached/P2P unless you explicitly want breadth.
3.10 Groups and Stream Expressions
Advanced filter stacks can define grouped conditions and expression-style logic.
Typical use:
- Build one group for baseline quality constraints.
- Build another group for language/codec requirements.
- Apply expression logic to combine them.
If your instance exposes Stream Expression Language (SEL), use this carefully:
- Complex expressions are powerful but easy to over-restrict.
- Always test with multiple titles after each expression change.
4) Sorting
AIOStreams sorting is hierarchical.
Primary sort contexts:
- Global (default fallback)
- Movies
- Series
- Anime
Cached/uncached split behavior:
- If configured, streams split into cached vs uncached groups.
- Each group can have its own sort stack.
- Group merge order follows cached sort direction.
Common criteria:
- Cached
- Resolution
- Quality
- Regex/Keyword rank
- Visual Tag
- Audio Tag
- Language
- Size
- Seeders
- Service
- Addon
Starter stack (quality + stability focused):
- Cached
- Resolution
- Quality
- Regex/Keyword
- Visual Tag
- Language
- Size
- Seeders
4.1 Scored Sorting (if enabled)
Some deployments expose score-based ranking in addition to regular hierarchical sorting.
Common pattern:
- Assign weighted points to quality signals (resolution, tags, cache state).
- Rank streams by total score.
- Keep a deterministic tie-break criterion (e.g., size or service) after score.
If scored sorting and standard sorting both exist on your instance, keep one as primary and use the other as fallback logic.
5) Formatter
Formatter controls stream title + description rendering.
Modes:
- Predefined format templates
- Custom template syntax
Template capabilities:
- Variable access (
{stream.*},{service.*}, etc.) - Chained modifiers
- Conditional output blocks
- Tool tokens (new lines, etc.)
The preview panel is non-destructive and should be used heavily before saving.
For full syntax, use the dedicated formatter guide:
6) Proxy
Optional stream proxy integration is available (e.g., MediaFlow Proxy / StremThru).
Use when:
- Upstream service/IP constraints cause failures.
- You need centralized outbound behavior.
Most proxy fields are self-described in UI and depend on your proxy backend.
7) Miscellaneous
This menu varies by version/instance and may include:
- UX toggles
- diagnostics behavior
- safeguards
- compatibility flags
Treat it as instance-specific advanced tuning.
8) Save & Install
Core operations:
- Create user config (UUID + password)
- Update existing user config
- Install to Stremio / Stremio Web / copy URL
- Export backup
Reinstall rules (important):
- Most internal config edits do not require reinstall.
- Changes that alter manifest structure often require reinstall:
- catalog reorder/type/name changes
- first time adding a new resource type
Presets You Can Start From
Preset A: Stable Daily Driver
- Timeout: 5s per addon
- Deduplicator: ON (
Single Result) - Cached preferred, uncached allowed
- Modest result caps
- No regex initially
Preset B: Quality Max
- Resolution required: 1080p/2160p
- Visual preferred: HDR/DV (ordered by your display preference)
- Size minimums per resolution
- Regex preferred list enabled
Preset C: Low Bandwidth / Mobile
- Exclude highest bitrates/sizes
- Prioritize smaller sizes
- Reduce result caps
- Disable noisy catalogs
AIOStreams + Wrapped Instances
Public-instance wrapping (AIOStreams-in-AIOStreams) is a community pattern for accessing addon combinations not enabled on one instance. If you use it:
- Keep credentials scoped correctly per instance.
- Document which UUID/password belongs to which layer.
- Re-test after upstream changes.
Troubleshooting by Symptom
- No streams: check addon enabled state, resource selection, and over-aggressive required filters.
- Too many duplicates: verify deduplicator detection + handling mode.
- Slow results: reduce timeouts and addon count; cap results.
- Wrong language: check language filters and sort priority.
- Install/update confusion: verify whether your change requires reinstall.
Post-Change Audit Tool
AIOStreams Configuration Checklist
Use this after saving your AIOStreams profile. The checklist is stored locally in this browser.