summary: a session is the time window edgeful uses as the reference point for your data. change the session, and you change what every report is measuring. this article covers what sessions are, the 4 built-ins, how time zones work, custom session setup, overnight sessions, and how to troubleshoot session issues.

sessions are one of the most important settings on the platform. a session defines the time window that edgeful uses to calculate everything — your gap reference close, your opening range, your IB window, all of it. it's not just a filter. it changes what the data is actually measuring.

sessions apply to futures, forex, and crypto. if you're trading stocks, edgeful always uses regular trading hours (9:30 AM to 4:00 PM ET) regardless of what session is selected.

trading outside Eastern time? start with choosing a session for your trading hours — it has a timezone-aware table, a decision tree, and step-by-step custom session setup for common international time zones.

prefer to watch first? Andre walks through how sessions and time zones work on edgeful — the local-timezone built-ins, how the session you select changes what reports like outside days, IB, and gap fill measure, matching your TradingView indicators to your session, and recreating the old Eastern-based sessions. the written sections below cover everything in the video.

open any report page, click the session dropdown, and select + create custom session. pick your timezone (e.g. Europe/Madrid, Asia/Tokyo, America/Los_Angeles), enter start and end times in that timezone, and save. if your window crosses midnight, edgeful handles that for you — there's no overnight setting to turn on. your end time doubles as the reference close — the level every report uses as "yesterday's close." full walkthrough below in creating a custom session.

Europe/London — 8:00 AM to 4:00 PM local, matching the London Stock Exchange. before the timezone update, the London session was anchored to Eastern (3:00 AM – 11:00 AM ET). if you prefer the old Eastern-based behavior, build a custom session in the New York timezone at 3:00 AM – 11:00 AM and name it "London NY." see reverting to the old Eastern-based sessions.

no — you don't need to convert anything. when you select the London session on a report, every time you see (open, close, IB window, etc.) is already in London local time. when you select the Asian session, the times are in Asian local time. only NY and Daily are anchored to Eastern time.

so if you're on a London session report and you see an 8:00 AM open, that's 8:00 AM London — not 8:00 AM ET. don't mentally subtract 5 hours; the platform has already done that conversion. the same applies to any custom session — it shows times in whatever timezone you chose when you created the session.

the only time you need to think about timezone conversion is when you're comparing a level on a London-session report to a level on a chart you've set to ET — those are 2 different timezones, so the displayed times will look different even though they refer to the same underlying market moment.

almost always a session mismatch — your selected session's IB or ORB window already closed hours before you sat down. switch to a session that overlaps your local trading hours. most European traders want London, most Asia/Pacific traders want Asian, and anyone outside those can build a custom session around their actual hours. full breakdown in choosing a session for your trading hours.

they just work — set your start and end times (say 10:00 PM to 6:00 AM) and save. edgeful treats the two halves as a single continuous window and calculates the reference close across the day boundary for you. there is no overnight toggle; if you remember one from an earlier version of the session setup, it's gone and there's nothing to switch on.

worth knowing about the built-in Asian session: it was an overnight session back when it was anchored to Eastern time. now that it runs in its own local timezone, the window no longer crosses midnight in Asian local time — even though it still falls in the ET evening and early morning.

edgeful's trading day doesn't start at midnight — it rolls over at 6:00 PM ET for futures and stocks, and 5:00 PM ET for forex and crypto. so a trade you place on Sunday evening at 7:00 PM ET (futures) counts as Monday data in reports. full explanation in the day rollover rule.

edgeful has 4 built-in sessions:

you can also create custom sessions in the reports section if your trading window doesn't match one of the built-in options.

edgeful now supports timezone selection for sessions. previously, every session on the platform was calculated using Eastern time (New York). now, each built-in session uses its local timezone — the London session runs in London time, the Asian session runs in Asian time, and so on.

what changed: the built-in London session used to be defined as 3:00 AM to 11:00 AM Eastern. now it's 8:00 AM to 4:00 PM London time, which matches the actual London Stock Exchange hours. the same applies to the Asian session — it now uses its local timezone instead of converting everything to Eastern.

what this means for the times shown on your reports: when you have the London session selected, all times displayed on that report are in London local time. Asian session selected = times shown in Asian local time. only the NY and Daily sessions show times in Eastern. you don't need to mentally convert — edgeful is doing it for you. if your custom session is set to the New York timezone, those reports show times in Eastern; if it's set to Europe/Madrid, they show in Madrid time. it's always whatever timezone the session itself is configured to use.

why the data can look slightly different: the old Eastern-based sessions and the new local-timezone sessions overlap almost perfectly — except during the days when daylight saving time changes don't line up between countries. London and New York shift their clocks on different dates, so there's a brief window each year (typically a few days) where the session boundaries differ slightly. on those days, you'll see minor differences in open, close, high, and low prices between the old and new session definitions. it's not that one is wrong — they're just measuring slightly different windows.

who this impacts: most NY session traders won't notice a difference at all. if you trade the NY session and that's it, nothing changes for you. the timezone feature primarily benefits international users who want to operate out of their local timezone instead of converting everything to Eastern time.

if you prefer the way sessions worked before — everything anchored to Eastern time — you can recreate that behavior with custom sessions. the key is setting the timezone to New York and using the old start/end times. the timezone picker shows named zones like "(UTC-4) New York", and those follow daylight saving, so a session set to New York stays on Eastern time all year.

for example, to recreate the old London session:

same idea for the Asian session — set the timezone to New York and use the old Eastern-time start/end (7:00 PM to 4:00 AM).

both approaches are accurate. you're just choosing whether to anchor to Eastern time or the session's local timezone. as long as you're referencing the correct open, high, low, and close prices for whatever session you've selected, the data works.

this is the most important thing to understand about sessions on edgeful. when you change the session, you're not filtering the same data to a different time window. you're changing the reference level that every report is built around. the question the report is answering literally changes.

a gap fill report on NY is asking: how often does price return to the previous NY close? a gap fill report on London is asking: how often does price return to the previous London close? those are 2 different price levels on the chart. the results won't just be slightly different — they'll reflect entirely different behavior.

the same principle applies to every report. the IB, the ORB, engulfing candles, outside days — all of them are anchored to the session you have selected.

the gap fill report measures how often price returns to the previous session close (PSC) — the closing price of the session you have selected, from the day before.

select NY and PSC is yesterday's 4:00 PM ET price. select London and PSC is yesterday's 4:00 PM London time price. select Daily and PSC is yesterday's 5:00 PM ET price. these are different levels. a gap that exists on NY might not exist on London, and vice versa. don't compare gap fill percentages across sessions — they're measuring different things.

the IB is the opening range of the session. you pick its length in customize, anywhere from 5 minutes to 3 hours in 5-minute steps, plus 4 hours, always measured from the session open. the session you select determines when it starts.

with a 60-minute IB, NY session means IB is 9:30 AM to 10:30 AM ET and London session means IB is 8:00 AM to 9:00 AM London time. if you trade the NY open and run the IB report on London session, you're looking at a range that formed hours before you were at your desk. always match the session to the open you're actually trading.

the ORB measures the opening range you set with the ORB timeframe in customize, starting at the session open. the session you select determines when that window starts.
​

with a 15-minute ORB, NY session means ORB is 9:30 AM to 9:45 AM ET and London session means ORB is 8:00 AM to 8:15 AM London time.

if your trading window doesn't match one of the built-in sessions, you can create a custom one. custom sessions let you define the exact time range and timezone you trade — so the reports measure what's actually relevant to you instead of a generic window.

note: custom sessions are not available on every report. to check if a report supports them, open the session dropdown on the report page. if you see "+ create custom session" as an option, it's available for that report. if you don't see it, that report only supports the built-in sessions.

here's how to set one up:

once saved, your custom session will appear in the session dropdown across all reports.

the timezone you pick for a custom session matters. a session set to 7:00 AM–3:00 PM in America/New_York is a different window than 7:00 AM–3:00 PM in Europe/London. make sure the timezone matches where you're actually measuring.

once you've created a custom session, you can edit it or delete it from the same place you create new ones.

the session is removed immediately and disappears from your session dropdown across all reports.

note: this only removes custom sessions you've created. the 4 built-in sessions (NY, London, Asian, Daily) can't be deleted.

use the same flow — open the session dropdown, select + create custom session, and the custom session window opens. from there you can update the timezone, start/end times, or name on any existing session.

bookmarks don't save the session — they save the report configuration but not the session selection. if you delete a custom session, your bookmarks keep working; they'll just open with whichever session is currently selected when you click them.

on report pages, you can hide sessions you don't trade and re-order the ones you do. to re-order, open the session dropdown and choose reorder sessions. the session selector then shows only what's relevant to your workflow.

this is a per-account setting — once you've set up your sessions on a report, the dropdown stays that way the next time you open it. what's in play and the screener still show their default session set; this customization applies to the report page selector only.

the NY session reference close on edgeful is the 4:00 PM ET price — the regular trading hours close. it is not the 4:15 PM ET futures settlement price, the 5:00 PM ET futures session close, or the 6:00 PM ET futures re-open.

this matters because if you're comparing what you see on edgeful to a level on your chart and they're slightly off, this is often why. the futures market keeps moving after 4:00 PM, so 4:00 PM, 4:15 PM, and 5:00 PM can all be different prices. edgeful uses 4:00 PM — full stop. the London reference close is now 4:00 PM London time. if data is filled after the session close, it doesn't count as a fill for that session.

edgeful's trading day doesn't start at midnight — it rolls over based on the asset class you're looking at:

what this means practically: if you're trading during the evening session and running a report filtered by weekday, the data corresponds to the following calendar day — not the current one.

this comes up most when you're using the weekday filter on a subreport, or when you're building a custom session that runs into the evening. if a weekday is showing unexpected results, check whether the rollover timing is affecting your data.

some reports let you filter by weekday, which is handy for studying day-of-week patterns. because the "day" follows the rollover and not the calendar, a trade at 7 PM ET on Thursday shows up under Friday's data. so when you filter for "Friday," you're getting everything from Thursday's rollover through Friday's rollover.

a few ways to use it:

the rule is simple: match the session to when you actually trade. if you trade the NY open — 9:30 AM ET — run your reports on NY. if you trade the European open — 8:00 AM London time — run your reports on London. if you trade the Asian session — overnight — run your reports on Asian. don't run reports on NY if you're trading London and expect the data to be relevant to your setups. the reference levels are different.

if none of the built-in sessions match your window, create a custom session with the right timezone and time range that captures your actual trading hours.

sessions show up across the platform — in reports, what's in play, and the screener. they work slightly differently in each area:

usually caused by either (a) wrong session selected — the PSC on your chart is from a different session than what edgeful is measuring, or (b) using 4:15 PM or 5:00 PM as a mental reference instead of 4:00 PM ET. switch to the right session and double-check your reference time.

Daily and NY look similar but use different reference closes (5:00 PM vs. 4:00 PM). if you're a NY session trader who accidentally has Daily selected, your gap fill levels and IB data won't match what you expect. switch to NY.

check the day rollover. if you're analyzing evening trades and expecting them to land on Thursday, they may be showing as Friday in the data because of the 6 PM ET (futures/stocks) or 5 PM ET (forex/crypto) rollover.

the built-in London and Asian sessions now use their local timezones instead of Eastern time. on most days this makes no difference — but during the few days each year when daylight saving time changes don't align between countries, the session boundaries shift slightly. if you want the exact same behavior as before, create a custom session in the New York timezone with the old Eastern start/end times (e.g., London at 3:00 AM–11:00 AM ET). see reverting to the old Eastern-based sessions above.

since the timezone update, the most common cause is a timezone mismatch between your edgeful session and your TradingView indicator. the other usual suspect is using the standard version of an indicator instead of the "by session" one. see sessions and your TradingView indicators below.

if your gap fill report is set to NY but your IB report is set to London, your levels won't align. keep all your core reports on the same session unless you have a specific reason to mix them.

60-minute candles start and end on the hourly mark, so the first 60-minute candle starts at 10:00 AM, not 9:30 AM. you can't measure 9:30–10:30 AM with a 60-minute candle. if you want to capture the first 30 minutes of the NY session open, use a 30-minute candle instead.

this happens when your reference time is set after the session open. the report tries to look up a candle that doesn't exist within the session range — and it can't. the fix is to set your reference time to something before the session start.

usually about contract rollovers. edgeful rolls to the next futures contract as volume shifts to it. if the other platform rolls on a different date or session times, the reference contract and prices will be different. check that both platforms are using the same contract month, and verify that the session settings match.

the session concept carries over to edgeful's TradingView indicators too. many indicators have a "by session" version, and the distinction matters:

same concept applies to previous day's range vs. previous day's range by session, pivot points vs. pivot points by session, and fibonacci vs. fibonacci by session.

if you're trading futures and your TradingView indicator levels don't match what you see on edgeful, this is almost always why: you're using the standard version of the indicator instead of the "by session" version. switch to the session variant and the levels will line up.

the timezone has to match too. whatever timezone your edgeful session uses, set your TradingView indicator's session to the same timezone and times. for example, if you're running the IB report on the London session, your TradingView IB indicator needs to use the same session start time in London time (8:00 AM) so the IB range plots correctly on your chart.

for the exact session and timezone values to enter for each session, see setting TradingView session times to match your edgeful reports (NY, London, Asia).

with the timezone feature, you no longer need to manually convert everything to Eastern time. you can set sessions in whatever timezone makes sense for how you trade. for which session fits your local hours (a local-time table, IB and ORB windows per session, and a decision tree), see choosing a session for your trading hours. to keep everything on Eastern time instead, see reverting to the old Eastern-based sessions.

the important thing is consistency: whatever timezone you pick in edgeful, use the same timezone in your TradingView indicators so your levels line up on the chart.