EVE Online embed map
EO-Map can sit inside another website as a chrome-free iframe of New Eden, or as a native JavaScript custom element. A wiki page, an alliance site or a killboard can show the same EVE Online starfield the full map draws, with host-driven navigation, highlights, routes and event flashes. There is no account, no download and nothing to install. The map is free.
What embed mode does
Embed mode is the same New Eden map, with the EO-Map chrome taken off so the starfield can live inside someone else's page. The iframe address is /embed. /?embed=1 is the same view. Native JS loads /embed/v1.js and mounts <eo-map>. A solar-system embed uses /solar-system/{id}?embed=1 on the iframe path, or a native mount with mode. Query parameters and mount options set the first camera, the first system, a 2D or 3D layout, security colouring, a gate route and highlight rings. After the map loads, the host keeps that one iframe or one native element alive and updates it instead of recreating it for every new system.
An Open on EO-Map control stays in the frame so a visitor can jump out to the full map. It is part of the product and should be left in place. The map is built from the pinned official EVE Online Static Data Export, build 3464040: 5,485 New Eden solar systems at their real positions. Jita is system id 30000142, which is the usual first example.
What you can put in the frame
3D galaxy view
The default. A true 3D starfield of New Eden, centred on a system you choose, with security-status colouring on unless you turn it off.
2D schematic
layout=2d morphs the same geometry into the flat New Eden layout. The choice is embed-only and does not write the visitor's full-app 2D or 3D preference.
Highlights and links
Accent rings on a set of systems, optional link lines between them, and optional overlay names. Nearby clusters read better than a map-wide set.
Gate routes
A point-to-point stargate route drawn on the embed, with an optional hop card. The host supplies origin and destination; the search still runs in the visitor's browser.
Solar system view
Drop inside one system for the star, its planets and its stargates. The embed=1 flag is required on that path, or framing is blocked.
Host-driven flashes
The host can flash a system it already knows about from its own feed. Kill-style red is the usual case; other colours exist. EO-Map does not open a kill source inside the embed.
The embed guide is the live showcase for both routes: copyable snippets, a builder with a sticky preview, and a feed demo. Switch Copy as to Iframe or Native JS. The iframe contract is embed-guide.txt. The native contract is embed-native.txt.
What it does not do
An embed is not the full application in a smaller window. The live-events WebSocket does not connect, so kills from EO-Map's own ticker do not appear on their own. EVE SSO is absent, so there is no character login inside someone else's page. Tools Library panels are ignored. The host supplies any event flash from a feed it already has. An iframe embed is still a page of eo-map.com, so Google Analytics records an anonymous page view the same way as the full map; the embedding site is not identified as a first-class dimension. The native JavaScript embed does not inject Google Analytics or EO-Map's own usage counters into the host page. Several WebGL maps on one page is a bad idea: use performance=1 and loading="lazy" when an iframe sits below the fold, and do not mount a grid of them. Native JS allows only one map per page.
How to open it
- Open the embed guide and copy a snippet as iframe or Native JS, or start from
https://eo-map.com/embed?system=30000142&zoom=50. - Place that iframe, or load
https://eo-map.com/embed/v1.jsand mount<eo-map>. Height around 450 pixels is a working first size. - Wait for
ef-map-ready(iframe) oreo-ready(native), then drive the same map: navigate, highlight, and flash systems from the host's own data. - Leave the Open on EO-Map control visible. Do not recreate the map for each update.
- If an LLM is writing the integration, point it at embed-guide.txt or embed-native.txt rather than at the React app.
Part of EO-Map
Embed mode is one way to open EO-Map's interactive 3D map of New Eden, not a second product. The stars in the iframe are the same 5,485 systems the full map draws from the pinned official Static Data Export. A visitor who clicks Open on EO-Map lands on the complete application, where the same session plans stargate routes, shows live kills and reads current alliance sovereignty.
Related tools
- Embed guide, the live showcase and builder with copyable examples.
- Native JS on the same Embed Guide. Pin /embed/v1.js. Contract embed-native.txt.
- 2D map, for the flat New Eden layout the embed can request with
layout=2d. - Route planner, for the same stargate routing a routing embed draws.
- Live kills, for EO-Map's own kill feed. An embed does not connect to that feed; the host flashes systems itself.
- Cinematic mode, for the presentation look whose tint and orbit options an embed can reuse.
- All EO-Map features.
Frequently asked questions
Can I embed an EVE Online map on my wiki?
Yes. EO-Map is free to embed on a wiki, alliance site or killboard. Use an iframe at eo-map.com/embed, or load eo-map.com/embed/v1.js and mount an eo-map element. The embed guide has copyable examples for both.
Does the embed show live kills on its own?
No. The live-events socket does not connect inside an embed, so EO-Map's own kill ticker does not run there. If the host already has kill or event ids, it can flash those systems with postMessage on an iframe or with map.flash on the native element. Absence of a flash is not proof that nothing died.
Can the embed be a 2D map?
Yes. Add layout=2d to the iframe URL, or layout: '2d' on a native mount, for the flat New Eden schematic. The default is 3D. That choice stays inside the embed and does not change the visitor's full-app layout preference.
How does the host change the system without reloading?
For an iframe, wait for ef-map-ready, then postMessage to the iframe's contentWindow. For native JS, wait for eo-ready, then call select, highlight and flash on the element. Recreating the map for every new system is the slow path.
Does embedding the map track my visitors?
An iframe embed is still a page of eo-map.com, so a production iframe records an anonymous Google Analytics page view the same way the full map does. The embedding site is not identified as a first-class dimension. The native JavaScript embed does not inject Google Analytics or EO-Map's own usage counters into the host page. EVE SSO is not shown in either.
Will it run on a modest page or a phone?
It needs a modern browser with WebGL 2.0. One iframe with performance=1 is the conservative choice on a CMS page. Add loading="lazy" when the frame is below the fold. Native JS allows only one map per page.