Bookmap vs ATAS: Heatmaps, Footprints and Trading Workflows

The short answer

Start with Bookmap if your recurring question is how resting liquidity changes around price. Start with ATAS if your process begins with footprint bars, volume distribution and session structure. This is a distinction between useful starting workflows, not a claim that either platform owns an exclusive chart type.

Bookmap lists footprint and DOM tools in its package comparison, while ATAS lists a heatmap offering. A simple “heatmap versus footprint” slogan therefore misses the overlap. The meaningful comparison is which workspace makes your main question easier to investigate, with the data and subscription you will actually use.

For individual introductions, read the Bookmap guide and ATAS guide. This comparison focuses on the choices that remain once you understand the basic tools.

At a glance

Table of contents

Resting liquidity and executed volume are different evidence

A resting limit order represents displayed willingness to trade at a price. A completed transaction represents an exchange that actually occurred. A volume profile summarizes transactions over a selected interval; it does not show an outstanding queue waiting to execute.

Bookmap’s core display puts a liquidity heatmap, executed-volume bubbles and the current book into a common visual setting. This makes it natural to follow the sequence around a price: an offer appears, persists, trades, refreshes or disappears.

ATAS’s footprint documentation starts with tick transactions aggregated at prices inside bars. Its volume, trades, bid-and-ask and delta views organize executed participation in different ways. The bar construction becomes part of the question being asked.

Neither evidence type automatically settles direction. A large offer can disappear without trading. Heavy buying at the offer can coexist with little upward progress. A useful workflow connects the order or transaction observation to what price does next.

How the same sequence looks in each workspace

Consider a hypothetical futures session approaching a previously marked high. Activity increases at that area, but price initially struggles to advance.

In a Bookmap-centered review, examine whether visible offers stayed in place, refreshed after executions or withdrew before price arrived. Then compare the transaction bubbles and subsequent movement. The history of displayed liquidity is central to that investigation.

In an ATAS-centered review, examine how bid-and-ask volume developed near the bar high, whether delta expanded without corresponding progress, and where activity accumulated within the selected profile. The footprint and session distribution organize the same event differently.

Write down the interpretation before advancing the replay. Then check the next sequence: did price accept higher levels, move back into the prior range, or remain undecided? This tests whether the display supported a usable observation at the time, rather than an explanation attached afterward.

The comparison is about information and decision timing. It does not imply that one platform would have produced a particular fill or profit in that hypothetical session.

Coverage starts with the feed, not the software name

Both products require a connection suited to the intended market. Bookmap’s connectivity guide distinguishes its software from data and brokerage services. ATAS describes its connectors as links to providers, brokers, exchanges and other trading infrastructure.

For a futures comparison, align the exchange, contract month, depth and session. For stocks, identify the venues behind the book. A subscribed venue’s depth is not automatically the full US equity market. For crypto, match the exchange and contract rather than treating similar ticker names as identical instruments.

Also separate live data from a live trading account. A simulated account can use live observations, while a software connection may support analysis without the order-routing arrangement you need. Determine these permissions before interpreting differences as a software advantage.

An efficient first test uses one instrument and a documented connection on each platform. Additional symbols and venues can be added once the baseline comparison makes sense.

MBO tools: entitlement and input must both match

Market by Order provides individual-order information beyond an aggregate quantity at a price. It can support more detailed analysis, but it is not created by purchasing a software tier.

Bookmap’s documentation separates the MBO Bundle from the compatible feeds required by its tools. It also notes that Stops & Icebergs Tracker is not supported on Nasdaq stock data. ATAS’s current plan comparison lists its own Iceberg, Stop Runs and Sweeps tools under specific access conditions.

Do not compare these capabilities by counting indicator names. Check the exact instrument, input feed, version and entitlement for the particular tool. A temporary inclusion or promotional add-on also needs to be distinguished from ongoing access.

For an initial evaluation, keep MBO analysis separate from the basic heatmap/footprint comparison. Establish what the ordinary book and transactions explain before judging how much an additional detector contributes.

Replay quality depends on what is being reconstructed

Bookmap documents recording and replay for studying market sequences. Before choosing an interval, determine whether the relevant historical depth and transaction detail are available through the intended recording or connection.

ATAS makes the reconstruction choice particularly explicit. Its Replay page distinguishes generated ticks and DOM, actual ticks with generated DOM, and actual ticks with historical DOM.

That is a substantive difference between practice tasks. Generated depth may help someone learn controls, but it cannot establish the precise resting orders in an original session. A footprint study needs reliable transaction detail; a historical pulling-and-stacking study needs appropriate depth history as well.

For a fair comparison, use the same event window, contract and session definition. Pause both reviews at equivalent moments. Change playback speed only after recording the initial observation, and evaluate order-entry practice separately from visual pattern recognition.

Platform versions and computer setup

Bookmap publishes system and adapter requirements, including Mac-specific connection information. A general operating-system label does not mean every adapter or add-on is available identically on every machine.

ATAS’s download page distinguishes Classic ATAS for Windows from ATAS X beta for Windows and macOS. It also warns that the full feature transfer takes time. Check the actual version needed for your workflow before using a broad “ATAS supports Mac” statement to settle the comparison.

Test under the intended workload: the chosen feed, number of symbols, displays and recording settings. A sparse demonstration chart is a different workload from several active full-depth instruments. Evaluate readability and responsiveness during the type of session you intend to study.

Compare the complete cost of the workflow

Use the Bookmap package comparison and ATAS pricing page to build two equivalent configurations. Bookmap distinguishes Global, Global Plus and Global Premium; ATAS separates its own feature tiers and access limits.

Price the required workflow rather than the most attractive introductory number:

1. Identify the software tier needed for the core display and execution controls.
2. Add the appropriate feed, exchange entitlements and subscriber classification.
3. Include only the add-ons or historical services required by the research question.
4. Compare the billing commitment, renewal treatment and any temporary inclusions.

A lifetime software purchase does not automatically cover future data charges or every separately supplied service. Conversely, a larger feature list provides little value if the extra tools never enter the process. Avoid ranking the platforms as cheaper or more expensive without stating the complete configuration being compared.

A practical evaluation plan

First, define the missing information. Write one recurring question that your current chart cannot answer. Choose either resting-liquidity behavior or transaction distribution as the initial focus.

Next, build small workspaces. In Bookmap, begin with the heatmap, transactions and current book. In ATAS, begin with a footprint, a normal price chart and a profile covering the same session. Keep display settings stable.

Then review comparable events. Record whether each view supplied a different observation before the outcome. Note reading errors, setup friction and unnecessary panel switching as well as useful insights.

Finally, decide what to retain. A platform should earn its place by improving a defined task. Using both is reasonable when one supports preparation and the other execution, but duplicated panels and extra connection demands need a clear purpose.

Which should you choose?

Choose Bookmap first when a time-based history of liquidity is the main missing part of your process and its data/adapter combination fits the instrument you follow.

Choose ATAS first when you want a chart-centered workspace built around transaction distributions, profiles and several views of the same session, with a version and plan that support the intended live connection.

Evaluate both when you can state their separate jobs. If both would simply provide another colorful confirmation of the same idea, start with one and refine the process before expanding it.

Common questions

Does ATAS have a heatmap, and does Bookmap have footprints?

Yes, their current product comparisons show overlapping capabilities. Availability and implementation depend on the package, version or add-on. Compare the actual configuration rather than relying on an older one-chart-per-platform description.

Can I reuse one data subscription across both?

It depends on the provider’s permissions and simultaneous-connection rules. A compatible provider name alone does not establish that two concurrent sessions are included. Confirm that arrangement with the provider before building a dual-platform setup.

Which is easier for a beginner?

The easier starting point is the one that answers a question you can explain. Someone thinking in bars and session profiles may find the ATAS workflow more familiar; someone following the persistence of visible orders may prefer Bookmap’s starting view. Both still require learning the underlying data.

Do I need both to trade futures?

No. Neither a pair of subscriptions nor a long indicator list is a requirement for a coherent research process. Start with the task, then decide whether one platform already covers it adequately.

Official sources

• Bookmap features
• Bookmap packages and access
• Bookmap connectivity and data scope
• Bookmap system and adapter requirements
• ATAS footprint views
• ATAS Replay reconstruction modes
• ATAS connections and demo data
• Classic ATAS and ATAS X versions
• ATAS plans and add-on conditions