ChartsPod Custom Timeframes: Keep Signal Timing and History Consistent
Custom timeframes can fit a market better than standard ones. They also change when signals occur and how much history each indicator has.
Short answer
When using custom timeframes in ChartsPod, keep three things consistent: bar boundaries (anchored to a fixed clock time such as 00:00 UTC so bars line up day to day), signal timing (alerts and backtests evaluate at the same bar close you analyse) and history (enough bars for each indicator's look-back). A 7-minute or 90-minute chart changes every indicator value compared with standard timeframes, so do not mix signals from different timeframes without labelling.
Three consistencies
| Aspect | Risk | Rule |
|---|---|---|
| Bar boundaries | Bars shift relative to sessions | Anchor to fixed UTC time |
| Signal timing | Alert evaluates on different bar than analysis | Same timeframe for alert and chart |
| History | Look-back exceeds loaded bars | Count bars available |
Signal timing
Control names in the terminal can change between releases. If a label differs from this guide, look for the setting that does the job described.
Choosing a custom timeframe
Pick a custom timeframe for a reason, such as dividing a session into equal parts or avoiding the crowded closes of standard intervals. Test it in replay and backtest before using it live, and keep it fixed for long enough to learn how indicators behave on it.
Example: indicator values shift
Illustrative: a 14-period RSI on a 60-minute chart reads 68 at 15:00 UTC. On a 90-minute chart anchored at midnight, the most recent closed bar ended at 13:30 and the RSI reads 61. Neither is wrong; they summarise different bars. An alert set on the 90-minute chart will not fire at the same time as a signal seen on the 60-minute chart.
Backtests on custom timeframes
Backtests must use the same custom timeframe and boundaries as live alerts, or results won't match live behaviour. See ChartsPod Backtesting: Set Fees and Slippage Before Comparing Results and ChartsPod One-Second Charts: Trade Coverage and Loaded-History Limits.
Set a custom timeframe anchored to UTC and check indicator warm-up.
Open the ChartsPod terminalAnchor custom bars to a fixed time, alert and backtest on the same timeframe, and confirm history covers each look-back.
Test Custom Timeframes on a perpetual chart; no account is needed to chart.
Launch ChartsPodQuestions readers ask
Why use custom timeframes?
To fit a market's rhythm or reduce crowding at standard intervals.
Do custom timeframes change indicators?
Yes, every value changes with bar boundaries.
How much history do I need?
At least the longest look-back × bar length.
Sources and methodology
ChartsPod capabilities were checked against its public overview, documentation index, markets and indicator pages on 17 October 2026. Exact control names inside the terminal can change between releases, so this guide describes what to set and check rather than quoting menu labels. Venue availability is shown per tool in the terminal. Worked examples use illustrative numbers.
- ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.
- TradingView Pine Script: Repainting — live vs historical calculation.
This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.
CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.