BullishReversalBeginner

Hammer

A small real body near the high with a long lower shadow after a decline.

Professional chart anatomy

Hammer

Illustrative example
Context
Downtrend
Confirmation
A subsequent close above the hammer high or broader resistance.
Invalidation
Break below the hammer low.
Educational chart, not live market data. Real formations vary in symmetry, duration and volatility.

What the market is communicating

Sellers drove price lower, but buyers recovered most of the session before close.

Volume behaviour

More meaningful with strong rejection volume.

Pro-trader lensDo not evaluate this formation in isolation. Compare relative strength, broader market regime, liquidity, volatility and nearby higher-timeframe levels.

Recognition checklist

  • Occurs after decline or at support
  • Lower shadow typically at least twice body
  • Small upper shadow
  • Close near upper range
  • Follow-through confirms

Quality improves when

Location is logical

The setup forms near a meaningful support, resistance or trend transition.

Structure is clean

Defining swing points are visible without forcing the label.

Participation confirms

Volume, volatility or relative strength supports the resolution.

Confirmation and trade planning

ConfirmationA subsequent close above the hammer high or broader resistance.
InvalidationBreak below the hammer low.
Target frameworkUse nearby resistance and risk/reward rather than candle height alone.
Best useIntraday · Swing

Aggressive versus conservative approach

AggressiveConservative
TriggerEarly boundary resolutionClose plus acceptance or retest
AdvantageBetter potential entryMore confirmation
Trade-offHigher false-break riskMay enter later or miss the move

Measured targets are planning references, not forecasts. Position size should be derived from defined account risk and the actual invalidation distance.

Failure modes and trader traps

  • Using it in an uptrend
  • Ignoring support context
  • Buying before follow-through

Looks valid—but may not be

A pattern can satisfy the visual outline yet fail because it forms in the wrong context, lacks sufficient touch points, breaks on weak participation or immediately returns inside the structure. A failed setup is information, not an exception to ignore.