OpenAI DevDay 2026: Start Time, Livestream Options, and What Developers Should Check

OpenAI DevDay 2026 is scheduled for Tuesday, September 29, in San Francisco. The official event page lists the opening keynote at 10:00 a.m. Pacific Time and says it will stream for free, with a reminder available by email signup. That is the confirmed start time for the keynote—not a published start time for every session. In-person applications are closed, so for most developers the practical choice is to watch live, follow official documentation during the announcements, or catch the recorded sessions afterward.

What time does the DevDay keynote start?

OpenAI lists the opening keynote for 10:00 a.m. Pacific Time on Tuesday, September 29, 2026, featuring Sam Altman. On that date, San Francisco is on Pacific Daylight Time. That converts to 1:00 p.m. Eastern Daylight Time, 5:00 p.m. UTC, and 12:00 a.m. on Wednesday, September 30, in Bangkok (ICT). If you are elsewhere, confirm the conversion in your calendar app and check that it labels the event in your own time zone.

The event page also lists breakfast at 8:00 a.m., breakouts and programming from 11:15 a.m. to 3:30 p.m., a closing session at 4:00 p.m., and a reception from 4:45 to 7:00 p.m., all in Pacific Time. Those are the on-site schedule items; OpenAI has only confirmed the opening keynote as livestreamed. Do not assume that the breakouts, workshops, or closing session will be available live.

OpenAI DevDay 2026: official schedule and livestream signup

Which way should you follow the event?

For a developer outside San Francisco, the live keynote is the simplest route if the hour works and the goal is to hear the opening announcements. Choose the replay if you need to inspect technical claims carefully, compare them with your own code, or watch with a team. In-person attendance offers a different kind of value—hands-on programming and direct conversation—but it is not an open walk-in option this close to the event. OpenAI says tickets are non-transferable and will not be sold at the door.

How can you watch the livestream?

Use the signup on the official DevDay page to request a reminder. As of September 27, OpenAI’s event page says the opening keynote will be livestreamed but does not identify a separate platform such as YouTube or publish a direct viewing URL in the schedule text. Treat the official event page and any reminder email from OpenAI as the source of the access link. Avoid relying on reposted links or unofficial countdown pages when the livestream destination has not been confirmed there.

The event page describes the online keynote as free and open to everyone. If you do not want to share an email address, you can check the official DevDay page again shortly before the start for any updated viewing instructions. OpenAI also says recorded sessions will appear on its site shortly after the event; the page does not give a precise upload time. A recording is therefore the more dependable option for people who cannot make the live slot, but it may not be available immediately.

What should developers check before and after the keynote?

Prepare a short list tied to a real project rather than trying to evaluate every announcement at once. The useful question is not simply whether a capability looks impressive; it is whether it changes what your application can do, what it costs, or what you must change to use it safely.

• Match announcements to a use case. Write down the task, current model or API path, a representative input, and what a successful result looks like. This gives you a baseline for a later comparison.
• Check availability and access. Confirm whether an announced model, tool, SDK, or feature is generally available, in preview, limited by region, or restricted to certain accounts. A stage demo does not by itself establish production availability.
• Read the API documentation and changelog. Look for the exact endpoint, model identifier, request fields, response behavior, SDK support, and migration guidance. OpenAI’s API changelog is useful for tracking what changed; the model catalog helps confirm current model details.
• Recalculate total cost. Compare the current API pricing with your actual traffic, including retries, tool calls, image or audio inputs, and longer outputs where applicable. A lower per-token price may not reduce total spend if the new workflow uses more calls.
• Check lifecycle and operational limits. Review deprecation notices, rate limits, latency, error handling, and the supported regions that matter to your service. Separate confirmed dates and limits from keynote descriptions that still need documentation.
• Plan a controlled evaluation. Run a small test set that includes ordinary cases, edge cases, and failures. Compare quality, latency, cost, and safety behavior against your current system before changing production traffic.

Keep a note of the source and date for each decision. Conference announcements can be useful signals, but the published API documentation, pricing page, changelog, and deprecation schedule are the references to use when you plan an implementation. If details are still missing after the keynote, mark them as unknown and wait for the documentation rather than building around an assumption.

Which option fits your situation?

Watch live if you can attend at the converted local time, want the keynote context, and are comfortable following a fast presentation. Wait for the replay if a precise technical read matters more than being first, or if you want to review the documentation alongside the recording. Use both if your team needs to capture the announcement and then decide whether it changes a roadmap: one person can note claims live while the rest evaluate them against the official docs afterward. Attend in person only if you already have a valid invitation and registration; the application window is closed.

For most builders, the practical sequence is simple: save the official event page, convert 10:00 a.m. Pacific to your local time, sign up for a reminder if useful, and prepare one concrete use case to evaluate. The keynote is the confirmed livestream; the recordings and documentation are the better tools for checking what is ready to build with.