Ichimoku Cloud: The Complete Indicator (and Its Limits in Crypto)
What Is the Ichimoku Cloud?
The Ichimoku Kinko Hyo (一目均衡表) — literally “one glance equilibrium chart” — was developed by Japanese journalist Goichi Hosoda in the 1960s. It’s designed to show support, resistance, trend direction, and momentum in a single view.
Unlike most indicators that measure one thing, Ichimoku gives you five lines and a shaded “cloud” area:
1. Tenkan-sen (Conversion Line) = (9-period High + 9-period Low) / 2
2. Kijun-sen (Base Line) = (26-period High + 26-period Low) / 2
3. Senkou Span A (Leading Span A) = (Tenkan + Kijun) / 2, plotted 26 periods ahead
4. Senkou Span B (Leading Span B) = (52-period High + 52-period Low) / 2, plotted 26 periods ahead
5. Chikou Span (Lagging Span) = Close, plotted 26 periods behind
The area between Senkou Span A and B forms the “Cloud” (Kumo).
How to Read It
The Cloud (Kumo)
- Price above cloud → Bullish trend
- Price below cloud → Bearish trend
- Price inside cloud → No clear trend, avoid trading
- Thick cloud → Strong support/resistance
- Thin cloud → Weak support/resistance, likely breakout zone
Key Signals
| Signal | Condition | Strength |
|---|---|---|
| Bullish TK Cross | Tenkan crosses above Kijun | Strong if above cloud |
| Bearish TK Cross | Tenkan crosses below Kijun | Strong if below cloud |
| Kumo Breakout | Price breaks above/below cloud | Trend reversal signal |
| Kumo Twist | Senkou A and B cross (cloud changes color) | Future trend shift |
| Chikou Confirmation | Chikou Span above/below price 26 bars ago | Confirms momentum |
The “Five-Line Confirmation”
The strongest Ichimoku signal occurs when all five elements agree:
- Price above cloud
- Cloud is green (Span A > Span B)
- Tenkan > Kijun
- Chikou Span above price
- Future cloud is green
In practice, getting all five is rare — and by the time all agree, much of the move is over.
Why Ichimoku Struggles in Crypto
Ichimoku was designed for daily charts on Japanese equities in the 1960s. The default parameters (9, 26, 52) correspond to:
- 9 = 1.5 trading weeks
- 26 = 1 trading month
- 52 = 2 trading months
Problems in Crypto
- 24/7 markets: The original periods assumed 6-day trading weeks. Crypto never closes
- Extreme volatility: Cloud gets crossed constantly, generating whipsaws
- Altcoin noise: Works better on BTC/ETH, nearly useless on small-cap alts
- Lag: The 26-period displacement means you’re looking at data from over a day ago on 1H charts
- Visual complexity: Five lines + cloud = information overload. Easy to see what you want to see
Backtest Reality
On 535 altcoins over 2+ years (1H timeframe):
- Pure Ichimoku signals (TK cross + cloud direction) produce profit factors below 1.0
- Too many signals in ranging markets (crypto ranges ~60% of the time)
- The lag means entries are consistently late
When Ichimoku Is Useful
Despite its limitations, certain elements work well:
- Kijun-sen as dynamic S/R: Better than simple moving averages for identifying bounce levels
- Cloud as trend filter: “Only short below the cloud” is a valid filter
- Kumo twist for regime detection: When the future cloud changes color, regime may be shifting
- Higher timeframes: 4H and daily charts reduce noise significantly
Adjusted Parameters for Crypto
Some traders modify the defaults for 24/7 markets:
Traditional: 9, 26, 52
Crypto 24/7: 10, 30, 60 (adjusted for no weekends)
Aggressive: 7, 22, 44 (faster signals)
There’s no consensus on “correct” crypto Ichimoku settings. Any modification should be backtested.
Key Takeaway
Ichimoku is a powerful visual framework for understanding market structure, but its default parameters don’t translate well to crypto’s 24/7 volatility. Use individual components (Kijun, Cloud direction) as filters rather than trading the full system.
Try combining Ichimoku’s cloud as a trend filter with other indicators in PRUVIQ’s Strategy Builder.
This is educational content. Not financial advice. Always backtest before trading.
Build Your Own Strategy
Combine indicators, set conditions, and backtest on 570+ coins with 2+ years of data. No code required.