A signal channel's win rate is not just about the entries it posts. It's also about how the subscriber configures their copier: risk %, TP splits, time filter, news filter, lot sizing rules. Two subscribers can copy the same channel with wildly different P&L because one of them is sizing 3% per trade with no SL fallback, and the other is sizing 0.5% with a 50-pip SL floor.
That's the problem we built Channel Presets to solve. Save a configuration once, get a public URL, share it anywhere. New subscribers apply it in one click.
What a preset is
A preset is a frozen snapshot of every option in a channel's Advanced Settings. That includes:
When you save a preset, all those fields get serialized into a JSON blob stored under a slug like gold-conservative or ftmo-100k-passing. Anyone with the URL /preset/gold-conservative can view every setting and apply it to their own channel.
Creating a preset
/preset/your-slug.You can update a preset after creation — applying a preset always copies the current version into the target channel.
Applying someone else's preset
You can still tweak any individual setting after applying — applying a preset is a starting point, not a lock-in.
Why this exists
Three real situations we saw repeatedly before launching presets:
1. Signal providers losing subscribers to bad config.
A new subscriber connects the channel, leaves all settings at default, sizes 5% per trade, and blows the account in two weeks. The channel's win rate was fine — the subscriber's risk was lethal. The provider gets blamed. Now the provider publishes a /preset/[their-channel] URL and pins it in the channel description.
2. Prop-firm passing configs.
The settings that pass an FTMO $100k challenge are extremely specific: 0.3% risk, 50-pip SL floor, news filter on, daily loss limit at 4.5%, max DD limit at 8%, FIFO on for some firms, time filter excluding the first hour of NY open. Nobody types all that correctly on the first try. Now there's a /preset/ftmo-100k-passing URL and you apply it in one click.
3. Backtested configs from blog posts.
We've published configs in blog posts before, listing each setting in a markdown table. Half the readers misread the table, the other half copied the wrong field. With presets, the blog post just links /preset/[slug] and the apply button does the work.
Discovering presets
The public preset directory is at [/presets](/presets). Each preset shows:
Sort by apply count to see what's working. The most-applied prop-firm preset and the most-applied gold preset are usually a good place to start if you don't have time to build your own.
A note on safety
Applying a preset overwrites your channel's existing config. You can undo by re-saving your old preset before applying a new one — that's why we recommend always saving your own current config as a private preset first. Two clicks, instant rollback if you change your mind.
We never let presets write code, run scripts, or change anything outside the channel-config schema. The worst case is "I applied a bad preset and now my channel sizes 2% instead of 1%." That's reversible in 30 seconds.
The bottom line
Most copiers force every subscriber to learn 40+ settings on their own. Channel Presets take the best configurations the community has discovered and make them shareable as a URL.
If you publish signals, [save your recommended setup as a preset](/presets) and pin the URL. If you subscribe to channels, browse what others have already validated. Either way, fewer subscribers blow accounts because nobody told them to set a sensible risk %.