Direct answer
Break and retest in forex describes a two-step sequence in price action: (1) price “breaks” through a predefined level, and then (2) later “retests” that same level. The idea is not that the move is guaranteed, but that traders can describe what happened in a repeatable way: first a level is exceeded, and later price comes back to interact with that level.
A key benefit is clarity. If you can state exactly what counts as the break, what level is being watched, what timeframe is used, and how you define a retest touch, you can independently check the pattern on charts—without relying on predictions. This also helps you distinguish stable mechanics (the sequence and definitions) from variable conditions (market volatility, spreads, and execution).
Mechanism and definition
The “level”
Break and retest always depends on a level that is defined in advance. In plain terms, a level is a horizontal (or near-horizontal) area on a chart that acts like a reference point. Examples of what people often choose as a level include a recent swing high/low or a range boundary. Because definitions vary, you should choose one method and keep it consistent.
Step 1: Break
The “break” means price crosses that predefined level. There are two common ways traders operationalize “cross”:
- Close-based: the candle closes beyond the level.
- Wick/touch-based: price touches or briefly exceeds the level even if the candle later returns.
These are not interchangeable. If you allow wicks to count, you will label more events as “breaks.” If you require closes, you will label fewer. Either can be used for checking, but the rule must be explicit.
Step 2: Retest
The “retest” is the later interaction where price returns toward the same level. Again, you need a definition:
- How close must price come (exact touch vs. within a tolerance range)?
- Does a retest require a candle close near the level, or is an intrabar touch enough?
- Must the retest occur after the break, or can it happen almost immediately?
In a simple model, the sequence is:
- price breaks level using your break rule;
- price later returns to the level using your retest rule.
Outputs you can observe
When you apply the rules to a chart, the “outputs” are factual descriptions:
- Whether a break occurred by your definition.
- Whether a retest occurred by your definition.
- Whether the market then moved away from the level (descriptive, not promised).
That last part matters: break and retest is often discussed as if it implies direction, but mechanically it is only a description of interaction with a level plus timing. Directional outcomes are variable.
A simple example you can verify
Assume the following fixed rules for checking (use them consistently):
- Level: the highest close of a prior 20-candle swing on your chosen timeframe.
- Break rule: a candle close must be above the level.
- Retest rule: later, price must touch or slightly penetrate the level area, within a small tolerance (for example, a few pips), after the break.
- Observation window: retest must happen within a set number of candles (so you avoid labeling extremely delayed returns).
Now, on a historical chart, you would look for the first candle that closes above the level (that is the break). After that break candle, scan forward until price comes back to the level area as defined. If price comes back and then moves away, you can describe it as “break and retest happened” under your checklist.
Two important points about this verification process:
- You are measuring occurrence, not predicting results.
- You can repeat the same checklist on multiple time periods or instruments to see how often your retest definition occurs and how outcomes vary.
Limitations and failure modes
Break and retest is vulnerable to several predictable problems, even when the definitions are clear.
False breaks
A false break happens when price crosses the level by your break rule but does not lead to a meaningful retest interaction that matches your retest rule, or the retest is immediate and then the market continues to move back through the level.
How to recognize it in a checklist-based way: your chart will show a break event, but the later interaction may be too weak, too delayed, or defined out by your retest criteria.
Wick-only “breaks”
If you treat a wick touch as a break, you may label many events that never produce a genuine structural change. This can inflate your number of “breaks” and make retest frequency look misleading.
Retests that are ambiguous
Markets are noisy. Price may hover around the level or interact in multiple small touches. If your retest rule is not explicit—especially what counts as “near the level”—you can end up with inconsistent labeling.
A stable approach is to define a tolerance and a requirement for timing (after the break) and for minimum contact (for example, at least one candle that reaches the tolerance zone).
Variable costs and execution realities
Even when the chart pattern is described correctly, real trading involves costs and execution conditions. Bid-ask spread, commission, and slippage can change what actually gets filled compared with a chart’s idealized candles. Since these factors vary across brokers, instruments, and jurisdictions, they affect the practical result.
No future promise from history
Historical instances of break and retest do not establish that the next occurrence will behave similarly. Treat the pattern as a descriptive framework you can test, not as an expectation of outcome.
Verification and next questions
To independently verify what you learn about break and retest, use a checklist with fixed rules:
- Choose a single level-definition method.
- Choose a break rule (close vs. wick/touch).
- Choose a retest rule (touch vs. close, tolerance, and timing window).
- Record what you observe: break present or not, retest present or not.
Then, ask additional questions that clarify the mechanics without turning it into a certainty:
- How sensitive are your labels to small changes in the tolerance?
- Does your retest rule change results more than your level-definition method?
- What happens when you test across different timeframes?
- Which failure modes (false breaks, ambiguous retests, immediate reversals) occur most often under your exact definitions?