Screening Event Schema Generator — Promote Film Screenings and Premieres

Generate valid ScreeningEvent JSON-LD with venue, film metadata, and ticket details. Clarify what’s showing, where, and how to attend.

Try the ScreeningEvent Generator

Why screening pages underperform

Pain points we solve

• Film name is mentioned in prose but not structured via `workPresented`.
• Venue lacks a proper Place object with address, hurting local relevance.
• Ticketing info misses price/currency/availability or a purchase URL.
• Hybrid/online screenings omit attendance mode and streaming/join URLs.

How SwiftSchema helps

Solution

The ScreeningEvent generator makes you capture the essentials: the film (via `workPresented`), start/end times with timezone, venue or VirtualLocation, organizer, and ticket Offers.

It produces clean JSON-LD you can paste on the screening page, pairing event details with the Movie metadata fans expect.

How it works

How it works

1. Choose ScreeningEvent in the generator below.
2. Enter screening title and film info under `workPresented` (name, URL, image, description).
3. Add start (and optional end) date/time with timezone, and venue as Place with address; include VirtualLocation for online.
4. Add ticket Offers with price, currency, availability, and purchase URL; include separate offers for VIP/GA if relevant.
5. Copy JSON or Script, paste on the screening page, and validate in the Rich Results Test.

Generate ScreeningEvent JSON-LD

Paste once per showing. Validate. Ship.

What is ScreeningEvent structured data?

ScreeningEvent is an Event subtype for film showings—premieres, festivals, limited runs, or community movie nights. It ties a specific screening to a Movie via

, clarifies when and where it plays, and how audiences can attend or buy tickets. Proper markup reduces ambiguity between different screenings of the same film and improves eligibility for event-rich displays.

Essential properties to include

• name
  — screening title; include film name and edition (e.g., “Opening Night: Film Title (4K)”).
• workPresented
  — Movie details (name, url, description, image) to anchor the screening to the film.
• startDate
  /
  endDate
  — ISO timestamps with timezone (e.g.,
  2026-04-08T19:00:00-05:00
  ).
• location
  —
  Place
  with venue name and PostalAddress; include
  VirtualLocation
  with join URL for online screenings.
• eventAttendanceMode
  —
  Offline
  ,
  Online
  , or
  Mixed
  for hybrid showings.
• eventStatus
  — keep accurate (
  EventScheduled
  ,
  EventCancelled
  ,
  EventPostponed
  , etc.).
• organizer
  — festival, cinema, or film society hosting the event.
• performer
  — speakers or guests (e.g., director Q&A).
• offers
  — ticket options with
  price
  ,
  priceCurrency
  ,
  availability
  , and
  url
  ; use multiple offers for tiers.
• image
  — poster or stills; aim for 1200px+.
• description
  — note format (IMAX/4K), language/subtitles, guest speakers, or accessibility.
• inLanguage
  — specify when screenings include dubbing/subtitles.

Implementation tips

• Use one ScreeningEvent per showing; do not combine multiple dates in one object.
• Keep canonical URLs stable; if a showing moves or cancels, update
  eventStatus
  and consider adding
  previousStartDate
  .
• Pair with
  Movie
  schema on the film page, and link from the screening page to the film detail page to reinforce context.
• If part of a festival, link to the festival page and consider
  EventSeries
  for multi-day blocks.

{
  "@context": "https://schema.org",
  "@type": "ScreeningEvent",
  "name": "Film Club: Inception",
  "startDate": "2026-04-08T19:00:00-05:00",
  "location": {
    "@type": "Place",
    "name": "Downtown Cinema"
  }
}