Forex session replay means loading a historical chart, choosing one defined Tokyo, London, New York, or overlap window, converting that window into the chart's timezone, starting before the session begins, and revealing candles without looking ahead. The purpose is to compare the same decision process across different dates—not to assume that a city label guarantees a particular pattern or profitable setup.
This page owns the session-selection and time-conversion problem. Use the separate structured replay-session guide for the complete bar-by-bar decision workflow. Use the forex historical-data guide when the question is data source, candle timezone, bid/ask conventions, missing bars, spreads, or replay accuracy.
Because spot foreign exchange is an over-the-counter market rather than a single exchange with one opening bell, Tokyo, London, and New York session hours are practical market conventions. Different brokers, chart platforms, and education sites may place a boundary an hour earlier or later. For repeatable practice, define one convention, record it, and keep it unchanged across the sessions you compare.
Key Takeaways
- Anchor a session to its local clock, then convert it to the chart timezone.
- Tokyo stays on JST; London and New York shift against UTC when daylight saving time changes.
- The United States and United Kingdom do not switch clocks on the same dates, creating short mismatch periods.
- Start replay before the selected session so the prior range and handoff are visible.
- Compare process and context across dates; do not treat a repeated visual pattern as proof of future performance.
- Keep session selection, full replay workflow, and historical-data quality as separate tasks.
Practice with ChartMini
Replay historical candles and train your trading decisions.
Forex Session Times: A Practical Replay Convention
The table below uses a common local-time convention for building consistent replay windows. It is not an official opening schedule for the decentralized spot FX market.
| Session | Local-time anchor | UTC during standard time | UTC during daylight time | DST treatment |
|---|---|---|---|---|
| Tokyo | 09:00–18:00 JST | 00:00–09:00 UTC | 00:00–09:00 UTC | Japan currently does not use DST |
| London | 08:00–17:00 London time | 08:00–17:00 UTC in GMT | 07:00–16:00 UTC in BST | UK clocks move in late March and late October |
| New York | 08:00–17:00 Eastern Time | 13:00–22:00 UTC in EST | 12:00–21:00 UTC in EDT | US clocks move in March and November |
Japan Standard Time is UTC+9. The National Institute of Information and Communications Technology, which maintains Japan Standard Time, states that Japan currently does not implement daylight saving time. The UK government lists the annual GMT/BST clock changes, while the US National Institute of Standards and Technology documents the US daylight-saving rules.
Do not copy a fixed UTC session box from an old screenshot and use it all year. Store at least these fields in the replay log:
Historical date:
Chart timezone:
Session local timezone:
Session local start and end:
Converted chart start and end:
DST state for London:
DST state for New York:
Session convention/source:
Choose the Session Before Choosing the Date
A session-specific drill should begin with a practice question. The session is the filter, not the strategy.
| Practice question | Session window to select | Suggested replay start | What to record |
|---|---|---|---|
| How does an Asian range form and hand off to Europe? | Tokyo and the Tokyo–London transition | 30–60 minutes before the Tokyo window | Range high/low, false breaks, handoff state |
| How does price behave around the European open? | London | 30–60 minutes before London local open | Prior Asian range, opening direction, rejected and accepted breaks |
| How does US participation change an existing move? | New York | 60 minutes before New York local open | London trend state, scheduled events, continuation/reversal decision |
| What happens when London and New York are both active? | London–New York overlap | 30–60 minutes before New York opens | Liquidity change, spread assumption, handoff, close of London |
| Does one rule behave differently by session? | The same local window across multiple dates | Same pre-session buffer every time | Rule adherence, no-trade decisions, costs and exceptions |
This table does not claim that one session is superior. A useful session is one that matches the exact condition you want to observe and can be repeated without changing the clock definition between samples.
London, New York, and Tokyo Are Context Labels—not Trading Signals
The SERP for forex-session queries is dominated by session-hour tables, overlap diagrams, pair examples, and claims about liquidity or volatility. Those elements help users orient themselves, but they can become misleading when presented as deterministic rules.
A session label tells you which financial center is active. It does not tell you that:
- a breakout will occur;
- a range will hold;
- a stop sweep must reverse;
- one currency pair will produce a minimum range;
- spreads will always be tight;
- a specific time window is profitable.
The Bank of England's 2025 BIS survey release confirms that the UK remained the largest FX center, with 37.8% of global turnover in April 2025. That helps explain why London hours matter as market context, but aggregate turnover does not predict the direction or quality of a particular historical setup.
Tokyo session replay
Use a Tokyo-window replay when the practice question concerns Asian-session structure, JPY-related activity, or the range handed to Europe.
A repeatable drill:
- Convert 09:00–18:00 JST into the chart timezone.
- Start 30–60 minutes before the chosen window.
- Mark the visible pre-session high and low without predicting the next move.
- Advance candle by candle through the session.
- Record whether the selected setup appeared, failed, or remained absent.
- Continue into the London handoff only when the handoff is part of the original question.
Do not assume that Tokyo must be quiet or range-bound. Compare the same variables across many dates and tag scheduled events, holidays, and unusual gaps separately.
London session replay
Use a London-window replay when the question concerns the European open, EUR/GBP-related participation, or how the Asian range is accepted or rejected.
A repeatable drill:
- Anchor the window to 08:00 London local time.
- Determine whether the historical date was GMT or BST.
- Start before the open so the Asian-session structure remains visible.
- Record the first accepted break, first rejected break, and any no-trade condition defined before replay.
- Stop at the planned London cutoff unless the London–New York handoff is explicitly part of the exercise.
Avoid labeling every move through the Asian high or low as a stop hunt. The chart alone does not reveal who traded, where actual stop orders were concentrated, or why a move reversed.
New York session replay
Use a New York-window replay when the question concerns US participation, scheduled US releases, or whether a London move continues, stalls, or reverses.
A repeatable drill:
- Anchor the window to 08:00 New York local time.
- Determine whether the historical date was EST or EDT.
- Check an official economic calendar before replay when the selected date includes a scheduled event.
- Record the London trend or range state before New York begins.
- Separate the event-release reaction from the later decision process rather than assuming the first move is false or the second move is genuine.
Historical candles may not reproduce executable bid/ask prices around fast releases. Use the historical-data quality checklist before drawing conclusions from narrow stops or short holding periods.
Daylight Saving Time: The Error That Breaks Session Comparisons
London and New York session labels stay tied to local clock time. UTC does not move. The conversion therefore changes when the local jurisdiction changes clocks.
For 2026:
- The United States uses daylight saving time from March 8 to November 1.
- The United Kingdom moves to BST on March 29 and returns to GMT on October 25.
- Japan remains on JST, UTC+9.
This creates two mismatch periods in 2026:
- March 8 through March 28: New York is on EDT while London remains on GMT.
- October 25 through October 31: London is back on GMT while New York remains on EDT.
During these periods, a replay template copied from the middle of summer or winter can be one hour wrong. That error can move the selected candle window, change which economic release appears inside the session, and distort a comparison with another date.
Safer DST workflow
- Store the historical date.
- Identify the city-local time zone, not a fixed GMT offset.
- Check the historical DST state for London and New York.
- Convert the local window into the chart timezone.
- Confirm the first and last candle timestamps before starting replay.
- Save the converted window with the session record.
Where software supports named time zones, prefer Europe/London, America/New_York, and Asia/Tokyo over manually entering fixed offsets. A fixed UTC-5 New York template is wrong during EDT; a fixed UTC+0 London template is wrong during BST.
Trading-Session Overlaps
An overlap is the part of the day when two local session conventions are open at the same time. It is useful as a context filter, not a promise of direction or execution quality.
Tokyo–London overlap
Using the table above:
- When London is on GMT, the overlap is approximately 08:00–09:00 UTC.
- When London is on BST, the overlap is approximately 07:00–09:00 UTC.
Some platforms define the Tokyo or London boundaries differently, so they may show a shorter or shifted overlap. Record the exact convention used by the replay tool.
London–New York overlap
Using the common 08:00–17:00 local windows:
| Clock state | Approximate UTC overlap |
|---|---|
| London GMT + New York EST | 13:00–17:00 UTC |
| London BST + New York EDT | 12:00–16:00 UTC |
| One city on daylight time and the other on standard time | 12:00–17:00 UTC |
The overlap is usually four hours and can temporarily become five hours during the US–UK DST mismatch weeks. OANDA's session guide similarly identifies the London–New York overlap as a high-activity period, but activity alone does not make every replay example representative or every simulated entry executable.
A useful overlap drill is to classify the state before New York opens:
London state: trend / range / failed break / unclear
Scheduled US event: yes / no / unknown
New York response: continuation / reversal / range / no clear response
Rule followed: yes / no / not applicable
Execution assumptions recorded: yes / no
A Session-Specific Replay Workflow
This is the minimum workflow needed to compare one session across dates. For the complete setup, decision-log, invalidation, no-trade, and review framework, use the structured replay-session guide.
1. Define one question
Examples:
- Does my written breakout rule appear during the first two London hours?
- How often is my setup absent during the Tokyo window?
- Does the same pullback rule behave differently before and during the London–New York overlap?
Do not begin with “find a winning trade.” That encourages date selection and hindsight.
2. Normalize the clock
Write the local session time, historical DST state, chart timezone, and converted replay window before selecting the first candle.
3. Include a pre-session buffer
Start 30–60 minutes before the selected window. The buffer is context, not an invitation to trade outside the planned session.
4. Hide future candles
Use historical replay rather than scrolling through a completed chart. TradingView's official documentation describes historical replay as a mode separate from live Paper Trading; the available features and saved results depend on the platform.
5. Record trade and no-trade decisions
At minimum record:
Date and session:
Local and chart timezones:
Setup and trigger:
Invalidation:
No-trade rule:
Decision:
Observed spread/cost assumption:
Scheduled-event context:
Rule adherence:
6. Stop at the planned cutoff
Do not extend the window until a setup appears or a simulated loss recovers. A session with no qualifying decision is valid evidence.
7. Review across comparable dates
Compare sessions only after confirming that their time conversion, data source, candle interval, cost assumptions, and selected window are consistent.
How This Page Is Separated From Related Guides
| Page | Owns | Does not own |
|---|---|---|
| This session-replay guide | Choosing Tokyo/London/New York windows, timezone conversion, DST and overlaps | Full decision workflow or data-feed validation |
| Structured replay-session guide | Setup definition, bar-by-bar decisions, no-trade log and process review | Forex session-hour definitions |
| Forex historical-data guide | Feed quality, candle timezone, bid/ask, spreads, missing data and replay limitations | Choosing which city session to practice |
| Forex replay software guide | Evaluating replay-tool features and limitations | Session-specific methodology |
This separation prevents three different questions from competing for the same page: when to replay, how to conduct the replay, and whether the underlying historical data is suitable.
Common Mistakes
Using GMT and UTC as if they always match London time
London uses GMT in winter and BST in summer. A label such as “London open at 08:00 GMT all year” shifts the summer window by one hour.
Converting New York with a permanent UTC-5 offset
New York uses EST and EDT. A permanent UTC-5 template is wrong during daylight time.
Treating Asian, London, or New York behavior as guaranteed
Session characteristics are distributions, not rules. Record setup-absent and contradictory examples.
Mixing session definitions between tools
One source may label an Asian session from Sydney open; another may anchor it to Tokyo. State which definition you use.
Comparing data from different chart timezones
Daily bars, session separators, and event timestamps can move when the feed or server timezone changes.
Ignoring scheduled events and holidays
Two sessions with the same clock window can have very different contexts. Tag scheduled events and holidays instead of attributing every difference to the session itself.
Frequently Asked Questions
What is forex session replay?
Forex session replay is a historical chart exercise built around a defined market window, such as Tokyo, London, New York, or a session overlap. The trader converts the window into the chart timezone, starts before the selected session, hides future candles, records decisions, and reviews how the same process behaved across different historical dates.
What times are the Tokyo, London, and New York forex sessions in UTC?
A practical local-time convention is Tokyo 09:00–18:00 JST, London 08:00–17:00 local time, and New York 08:00–17:00 Eastern Time. That converts to Tokyo 00:00–09:00 UTC year-round; London 08:00–17:00 UTC in GMT and 07:00–16:00 UTC in BST; and New York 13:00–22:00 UTC in EST and 12:00–21:00 UTC in EDT. Providers may label session boundaries differently, so verify the convention used by your chart or broker.
Why do forex session times change with daylight saving time?
London and New York keep their session labels tied to local clock time, while UTC does not change. The United Kingdom and United States also switch daylight saving time on different dates, so UTC conversions and overlap length can shift during the transition weeks. Japan Standard Time remains UTC+9 and Japan does not currently use daylight saving time.
When do the London and New York forex sessions overlap?
Using the common 08:00–17:00 local-session convention, London and New York usually overlap for four hours: 13:00–17:00 UTC when both cities use standard time, or 12:00–16:00 UTC when both use daylight time. The overlap can temporarily last five hours when the United States and United Kingdom are on different daylight-saving schedules.
Which forex session should I replay?
Replay the session that matches the market condition and schedule you want to study. Tokyo can be used for Asian-session range and JPY-pair observation, London for the European open and EUR or GBP activity, New York for U.S.-session and scheduled-release context, and the London–New York overlap for cross-session continuation or reversal practice. No session is automatically best or profitable.
Is session replay the same as a complete replay workflow or historical-data testing?
No. Session replay selects and normalizes the market window being studied. A complete replay workflow defines the setup, decision log, invalidation, no-trade rules, and review process. Historical-data testing focuses on feed quality, candle timezone, bid and ask conventions, missing bars, spreads, and other data limitations. The three roles are related but should be documented separately.
Official Sources Checked
- Bank for International Settlements: 2025 Triennial Central Bank Survey
- Bank of England: 2025 UK FX survey results
- UK Government: annual GMT and BST clock changes
- US National Institute of Standards and Technology: daylight-saving rules
- NICT Japan: Japan Standard Time
- TradingView: trading on historical data in Bar Replay
- OANDA: forex trading sessions and overlaps
Related Reading
- Run a complete day-trading replay session
- Check forex historical-data quality before replay
- Compare forex replay software
- Choose a replay speed for deliberate practice
- Log simulated decisions during replay
- Open the ChartMini replay workspace
Practice with ChartMini
Replay historical candles and train your trading decisions.