Forex Session Replay: London, New York, and Tokyo

Quick answer: forex session replay means choosing a historical London, New York, Tokyo, or overlap window, converting that window for the exact historical date, hiding future candles, and reviewing the same decision process across comparable sessions. The city label is a time filter—not a trading signal or a promise of a profitable setup.

This page owns one narrow problem: how to define and replay a specific forex session without mixing time zones or daylight-saving states. The forex market-hours guide owns the weekly schedule, holidays, rollover, and clock availability. The best-time-to-trade guide owns suitability and window selection. The structured replay-session guide owns the full bar-by-bar decision workflow, while the forex historical-data guide owns feed, Bid/Ask, spread, missing-bar, and data-quality checks.

Spot FX is an over-the-counter market rather than a single exchange with one official opening bell. Tokyo, London, and New York session hours are therefore practical conventions. Different brokers and chart platforms can place a boundary differently. For repeatable replay, choose one convention, record it, and keep it unchanged across the samples you compare.

Key Takeaways

Anchor the replay window to the session's local clock, then convert the exact historical date into 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 switch clocks on different dates, creating short mismatch periods.
Use the same pre-session context rule, session cutoff, and review fields across every sample.
Treat Tokyo, London, New York, and overlap labels as context filters—not signals or profitability claims.
Exact session replay requires date/time navigation; ChartMini currently randomizes the Forex pair and historical starting point, so it is better suited to blind chart-reading practice.

How to Replay a Specific Forex Session

Use this five-step sequence before comparing London, New York, Tokyo, or overlap samples:

Define the session in local time. Record the city-local start and end used by your data provider or replay tool.
Choose the historical date. Resolve the daylight-saving state for that date before converting the window.
Convert into the chart timezone. Confirm the first and last candle timestamps rather than relying on a fixed UTC offset.
Hide future candles and keep one context rule. Start before the selected window using the same predefined context buffer in every sample.
Stop and review at the planned cutoff. Record setup-present and setup-absent sessions with the same fields; do not extend the window until a trade appears.

Session times for a consistent replay convention

The table below uses one common local-time convention for building repeatable 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 a Replay Question, Not a “Best Session”

A session-specific drill should begin with a written practice question. The session is the filter, not the strategy.

Practice question	Session window to select	Context to preserve	What to record
How does an Asia-to-Europe handoff develop?	Tokyo and the Tokyo–London transition	The same pre-session context window on every sample	Range state, accepted/rejected breaks, handoff state
How does price behave around the European open?	London	The prior Asian-session state	Opening state, accepted/rejected breaks, setup present/absent
How does US participation interact with an existing move?	New York	The London state plus scheduled-event context	Continuation, reversal, range, or no clear response
What happens while London and New York are both active?	London–New York overlap	The London state before New York begins	Handoff state, event context, decision and no-trade outcome
Does one written rule behave differently by session?	The same local window across multiple dates	The same clock definition and context rule	Rule adherence, no-trade decisions, costs and exceptions

This table does not claim that one session is superior. A useful replay window is one that matches the exact question you want to study and can be repeated without changing the clock definition, context rule, or review fields 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 before the chosen window using the same predefined context buffer in every sample.
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: Convert the Historical Date, Not a Fixed Offset

London and New York session labels stay tied to local clock time while UTC does not move. The conversion therefore depends on the historical date.

Current clock rules provide a safer replay anchor than memorizing one UTC table:

In the United States, daylight saving time currently runs from the second Sunday in March to the first Sunday in November, subject to local exceptions documented by NIST.
In the United Kingdom, clocks currently move forward on the last Sunday in March and back on the last Sunday in October.
Japan Standard Time is UTC+9 and Japan currently does not use daylight saving time.

For a 2026 example, US daylight time runs from March 8 to November 1, while the UK uses BST from March 29 to October 25. That creates two temporary US–UK mismatch periods: March 8–28 and October 25–31.

A replay template copied from the middle of summer or winter can therefore be one hour wrong during a transition period. That error can move the selected candle window, change which scheduled release appears inside the session, and make two historical samples look comparable when their clock definitions are not.

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. Use one pre-session context rule

Start before the selected window far enough to preserve the context required by your written rule, then use that same context definition in every sample. The buffer is context, not an invitation to extend the trading window.

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.

Where ChartMini Fits

ChartMini's current Forex Trading Simulator intentionally selects a supported currency pair and historical starting point at random while keeping later candles hidden. That makes it useful for blind chart-reading and directional-decision practice, but it is not an exact-date or exact-session navigator.

If your research question requires a specific London, New York, Tokyo, or overlap window, use a replay tool that lets you select the historical date and time, then apply the clock-conversion and review record in this guide. Do not describe a random ChartMini session as a London-session test unless the resulting timestamps actually match the predefined window.

Page	Owns	Does not own
This session-replay guide	Defining and replaying Tokyo/London/New York windows, historical-date conversion, DST and overlaps	General market availability, “best time” claims, full workflow or feed validation
Forex market-hours guide	Weekly availability, session clocks, weekends, holidays, rollover and server-time issues	Session-specific replay methodology
Best-time-to-trade guide	Choosing and validating a suitable trading window for a pair and written rule	Exact replay procedure
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 keeps three nearby questions distinct: when the market is available, which window fits a rule, and how to replay a chosen session without clock or hindsight errors.

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?

There is no single official spot-FX session schedule because the market is decentralized. For repeatable replay, this guide uses Tokyo 09:00–18:00 JST, London 08:00–17:00 local time, and New York 08:00–17:00 Eastern Time. That maps to Tokyo 00:00–09:00 UTC year-round; London 08:00–17:00 UTC in GMT or 07:00–16:00 UTC in BST; and New York 13:00–22:00 UTC in EST or 12:00–21:00 UTC in EDT. Record the convention your chart or broker uses before comparing sessions.

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?

Choose the session that matches a written research question rather than a claim that one session is best. For example, use Tokyo to study an Asia-to-Europe handoff, London to study the European open, New York to study U.S.-session context, or the London–New York overlap to compare a handoff while both centres are active. Keep the same clock definition and review fields across samples. No session is automatically profitable.

Can I choose an exact London, New York, or Tokyo session in ChartMini?

Not currently. ChartMini's Forex Simulator randomly selects a supported currency pair and historical starting point, so it is suited to blind chart-reading practice rather than exact-date or exact-session navigation. For a specific London, New York, Tokyo, or overlap replay, use a tool that lets you choose the historical date and time, then apply the timezone and review workflow in this guide.