Design once. Publish every seating surface.

Rows, tables, sections, floors, price zones and accessibility in one chart. Publish it once; the buyer picker, optional 3D view, live inventory and box office read the same revision.

SeatLayer is a seat map designer whose output is a published, versioned venue document rather than a drawing. Use it hosted, embed it in your own product with an origin-scoped session, or drive it from the seat map API.

GRAND THEATRE · DESIGNER Illustration
Four jobs in one editorseat the room · explain the space · prepare inventory · represent accommodations

One editing model for the whole room.

Four jobs, one chart: seating geometry, venue structure, commercial meaning, and inclusive selection. Publish freezes a revision; buyers and live inventory only ever read published revisions.
Publishing and versioning ↗

GEO

Seat the room

Straight, curved, or fanned rows; round and rectangular tables; booths; GA capacity areas inside a reserved-seat chart; and reusable seating blocks. Pure-GA production events are not supported.

  • True arc and fan geometry
  • Flip or serpentine numbering
  • Align, distribute, and precision select
MAP

Explain the space

Sections, floors, focal points, shapes, labels, surroundings, and buyer-visible backgrounds describe how the venue is organized.

  • Multi-floor structure
  • Section outline and labels
  • Best-available focal point
SELL

Prepare inventory

Categories, ticket tiers, per-seat overrides, and chart validation turn drawn geometry into an event-ready seating model.

  • Category paint
  • Ticket tiers and price zones
  • Warnings before publication
A11Y

Represent accommodations

Buyer-filterable accessibility types include CART, while wheelchair inventory distinguishes a physical accessible seat from an empty wheelchair bay.

  • Buyer-visible filters
  • Physical seat or empty bay
  • Labels carried into selection

Import a venue plan: trace an image or a supported vector

Reference files help you align the chart; the seating document stays an intentional model of rows, tables, sections, labels and shapes. A PNG, JPEG or WebP can sit underneath as a private trace reference, and for a PDF you choose one page from a source up to 15 MB and 100 pages, which is rasterized for tracing. The reference never becomes the chart: it stays private to the editor and out of anything a buyer sees. Already selling on another system? Import a chart that is already public and keep going.

Reference-plan import guide ↗
PRIVATE TRACE REFERENCE

Trace a selected plan page.

Use PNG, JPEG, or WebP, or choose one selected PDF page from a source up to 15 MB and 100 pages. That PDF page is rasterized into the private trace layer; it is not native PDF or vector conversion.

The private trace layer is independent from an optional URL-only buyer background. Trace bytes and provenance never reach the buyer renderer.

EDITABLE VECTOR SUBSET

Convert supported primitives into shapes.

A bounded SVG/DXF subset is sanitized and converted into ordinary editable Shape objects. This is not arbitrary SVG or full CAD fidelity, and it does not add SVG export.

Downloadable chart PDF output is a clean chart render, not source-PDF round-tripping.

Choose a shape close to the room you need.

Every template opens in the same Designer. Replace geometry, labels, categories, and capacity until the chart matches the venue.

Ask the chart. Then tell it what to change.

Copilot reads the chart already open in the Designer. Every normal tool keeps working; Copilot proposes, and you decide what publishes. The full set of AI seating chart capabilities, with the state of each one, is published separately.

Ask · available

Ask about the open chart

Capacity, a floor, what needs review — the answer names the chart context so you can inspect it yourself. Ask never moves geometry or publishes.

Try Ask in the demo Designer ↗
Edit · available

Change it by asking

Copilot can change the open chart when you ask it to, and every change is a reviewable revision you publish. A plan or reference image can be its input.

What Copilot does today →
Designer MCP · available

Bring your own agent

A compatible MCP client works through one authorized chart scope. Permissions, revisions, validation and publishing stay with SeatLayer and the person.

Connect an agent →

An embeddable seat map designer for your product

Open the Designer inside your own product with a short-lived dse_ session for one organizer workspace, chart and origin. Your server mints it with a server-only sk_ credential; the secret never reaches the Designer iframe.

SESSION BOUNDARY
Credential
dse_ in the browser; sk_ server-only
Scope
One workspace, chart and origin
Events
Ready, save, publish, close
Publish
Explicit permission
Revocation
Immediate session invalidation

What teams usually need to know.

Open the playground for hands-on evaluation, or use these answers to choose the right path.

Can I use the Venue Designer without signing up?
Yes. The Designer playground opens without signup. You can work in the browser and create an account when you want cloud continuity, publishing, or team workflows.
Does the same chart power 2D and 3D?
Yes. SeatLayer publishes one venue document. The buyer experience can use the complete 2D Map and optionally add the geometry-generated 3D view.
Can I trace a venue plan?
Yes. PNG, JPEG, or WebP can be used as a private trace reference. For PDF, choose one page from a source up to 15 MB and 100 pages; that page is rasterized for tracing.
Can a ticketing platform embed the Designer?
Yes. JavaScript and React hosts can open an origin-scoped Designer session for one workspace and chart, with explicit save, publish, close, and revocation controls.
What is a seat map designer?
It is the tool that builds the seating model a ticketing system sells from: rows and curved rows, tables, booths, sections, general-admission areas, floors, price categories and accessibility marks, held in one venue document. A seat map designer differs from a drawing tool because its output is structured and versioned — the buyer picker, the optional 3D view, live inventory and the box office all read the same published revision, so the chart is designed once and reused for every event in that room.
Can I embed the seating chart designer in my own product?
Yes. Your server authorizes the host user, decides their Designer authority, and mints a short-lived dse_… session bound to one workspace, one chart and one origin; the SDK mounts the returned designer URL and validates messages. Your product reacts to ready, saved, published, close and error events, replaces the session before or after expiry, and revokes it immediately when access ends — so organizers edit charts inside your CMS without a SeatLayer login each. The embedded designer guide has the end-to-end flow.
How is a seat map designer different from a floor-plan or drawing tool?
A drawing tool produces a picture: shapes on a canvas that look like a room. A seat map designer produces a structured, versioned document in which every row, seat, table, booth, section, floor, price category and accessibility mark is an addressable object — which is what makes the same chart sellable. That structure is why one published revision can drive buyer selection, the optional 3D view, live inventory, the box office and reporting at once, and why changing the room is a new reviewed version rather than an edit underneath a running on-sale.
Does the designer have an API?
Yes, at two levels. Your backend uses a server-only sk_ credential to mint a short-lived dse_ Designer session; the browser receives only that origin-, workspace- and chart-scoped session. Published charts are addressed by the rest of the platform: a public buyer picker uses { event, publicKey } for direct public bootstrap, while a private audience replaces publicKey with a token provider. Separately, Designer MCP lets a compatible MCP client work through one authorized chart scope using deterministic tools, validation and review gates; permission, canonical revisions and publishing stay with SeatLayer and the person, and a session may publish only what it was explicitly permitted to.

Start with venue geometry. Publish a reusable seating chart.

Try the Grand Theatre in the live Designer, or talk with us about authoring inside your ticketing or venue workflow.