Hello everyone and welcome to our builder keynote. You may know me from such events as the keynote also this morning, I'm Jess Fain, VP of Product here at Webflow. And I'm Alexander, I lead the brand studio here at Webflow. This morning we shared how Webflow is evolving to support marketing teams in the age of AI, expanding support for agentic development, unlocking new tools, helping marketers and agencies grow, and previewing Source by Webflow, a new code native platform for your whole team. That's exciting, but for those of us doing day to day work in Webflow, concrete quality of life improvements can be just as important. Since last Webflow Conf we've shipped 151 individual improvements, basically all from you, the forum, the wish list, time we spend with you weekly, fun conversations on Reddit as builders, these transform what we can do and how well. That's why we're celebrating our community of builders showcasing our latest investments in making Webflow a delightful place to design and build. You'll hear from Webflowers who helped bring these to life,

kicking off with Jake. On every site you build there are certain UI patterns you create over and over, visitors expect them, they make content feel professional and easy to navigate, but getting details right can be tricky, especially accessibility and layout, like building a simple tooltip or dropdown that turns into wrestling with z-index. That's finally over. In a few weeks we're rolling out new building blocks for common UI patterns, starting with popovers. Native popover support lets you build modals, tooltips, banners and menus, no custom code, no workarounds, built on modern web features like top layer and anchor positioning instead of JavaScript, pages stay lighter and more accessible, and you can stop relying on our old dropdown element and its jQuery. Anchoring on web standards was important for a solid foundation to build encapsulated components, easier for marketers to use popovers in build mode, and since AI is fluent in code, easier for AI agents to help create in Webflow too. Popovers roll out later this month, sign up today for the beta. Later this year we'll go further with native support for more patterns, repeaters for tabs and accordions, sliders and more. Even though those make common things easier, sometimes you need to break out of the box for more creative UI, something needing JavaScript. AI generated code components are perfect for that, say I need an interactive ROI calculator for a product comparison page, instead of filing a dev ticket I describe it to the Webflow AI assistant, roughly what it should calculate and look like, and it builds a real component on the canvas. But getting AI agents to deliver a perfectly styled component can be tricky, so today we're releasing visual editing for AI code components, you can style and fine tune them directly on the canvas like anything else in Webflow, if spacing feels off, click in, select the element, use the style panel to adjust, or drop that as context so the AI assistant scopes its next change to just that piece, bringing advanced functionality onto your page without giving up design control. Visual editing for AI code components is available to all users starting today. Thanks Jake, components are essential building blocks but what you build with them matters. When you're writing a blog post and realize you need more than rich text, a CTA button, testimonial card, pricing table, you stop writing and bother a coworker for help, as a marketer I've been in this situation more than I'd like, until now that meant cobbling a not-great solution or hassling coworkers like Alexander, sorry. Today we're launching components in the CMS, drop a component directly into rich text on the canvas or in CMS items and configure it for that specific content, easier for marketers to optimize CMS content, and for agencies, easier handoff to clients, build a customer quote component once and hand it to the client's marketing team, they add it to posts by swapping quotes and names through props, nobody codes or messages you frantically. This isn't limited to simple components, remember the interactive ROI calculator, an AI generated code component, now use it just like any other component in the CMS, drop it into a post, configure inputs through props, reuse it anywhere, each instance belongs to its own CMS item, the same calculator can work in different blog posts with different content, and if you update the design it applies everywhere at once, with right guardrails someone like me can update content without wreaking havoc. Components in the CMS roll out today, available to all users in the next week. Now that components are dropping everywhere, I want the right structures and guardrails for success, that ROI calculator doesn't deserve to be in a slot on a card component, when you build sites you know exactly how each component should be used, but it's awkward to say don't pay attention to these components, feels scary to hand over your site no matter how well documented. Over the last few weeks we shipped features to create that structure upfront. First, Hide Show Control for marketers, control exactly which components are available in build mode, keep complex or technical ones out of view entirely. Second, slot restrictions, restrict which components are available in which slot, if my ROI calculator only belongs in that comparison post layout, make sure that's the only place it goes, marketers get freedom to build without breaking the page. We're not done, later this month, default components for slots, when you drag a card component onto the page it automatically comes with a button component in the slot ready to customize, not staring at an empty slot with no indication or rebuilding the same setup from scratch, you can always replace content in that slot, but with default slot content your intended use case is baked in while keeping flexibility. These guardrails apply whether working directly on canvas or agentically through MCP, your site stays on brand no matter who's editing. Thank you Jake for making my life easier, to be honest it'll make mine easier too, default components for slots available later this month. As builders we spend a lot of time on the canvas, working across hundreds of pages, locales, components, variants, building structure for scale, fine tuning design details, QA across all these contexts, ensuring design and build quality tailored to every device, managing all these workflows means holding immense context in our heads, a lot of context switching, but getting it right matters to us and to clients, customers, stakeholders. Over the past few months our team worked to minimize context switching on the canvas, faster and easier to achieve your bar of quality without holding all that context in your head. We released improvements: components got a canvas of their own, see component variants side by side, spacing, margin and padding now show up visually on the canvas not just numbers in the style panel, and we brought pan and zoom to pages, many of you asked why we need that on a page, when there's more than one frame. Today I'm excited to announce Webflow's new Breakpoint Canvas, every breakpoint on the canvas side by side in a single view, instead of clicking desktop then tablet then mobile and back hoping you didn't break something, now you see the whole responsive picture together, all changes cascade in real time, and you can pan and zoom between frames, zoom in on a detail, zoom out for the full view, making responsive design easier while building, and making AI agent changes easier to review across devices to maintain design consistency without constant context switching. Breakpoint Canvas starts rolling out today, available to all over the next week. Hearing about Breakpoint Canvas reminds me of that old CSS meme where the window shade won't stay down, you check a million places for a change and still miss something, locales can be like that too, I wish I could tell you in six languages what's new with Webflow Localize but I haven't gotten that far in my language app. For organizations serving multinational or multilingual audiences, localizing design and content is key to a first class experience, so we've been improving Webflow Localize to make this smoother and more reliable. We started under the hood making fundamentals stronger so site structure stays in sync across locales, then a tiny but mighty bonanza of improvements, builders now have more control over how component properties are translated in secondary locales and custom code blocks, and you can tune your site's tone and formality per target language because localization isn't just translation, it's subtle cultural shifts too. Speaking of translation, Webflow Localize brought visual editing to localization so web teams don't wrangle JSON files full of strings, internet elders know what I mean, still translating content is pretty manual even with on-demand AI assistance, agencies tell us it can take months to stand up a new locale for a client, ouch, but what if it could happen in minutes? Agentic translation reduces thousands of clicks down to set it and forget it configuration, once enabled copy updates automatically reflect across every language on your site, no babysitting AI or reminding team members to translate blog posts while publishing, content is translated in real time. A beta tester said they stood up two locales with fully translated content in five minutes yesterday, awesome. For teams wanting tight control, use automatic translations as a first pass then fine tune by hand, with agent-human collaboration translations become orders of magnitude faster, accelerating launches with more effective ROI. Agentic translation rolls out in a few weeks. This is a big unlock for teams having this much control over localized content, launching in new markets is tough enough, personally excited for folks to get their hands on it, and selfishly for our team too, the speed to market gains are massive and important for meeting the moment. Speaking of speed, now hearing from Dustin need for speed Kasten. Like you we use Webflow to build our brand and marketing sites every day, how many have had that experience clicking something in the designer and just waiting, or copy pasting and seeing the spinning beach ball, or timing publishing with a coffee refill, needing time for a pour over, unfortunately that's what using Webflow too often felt like, nothing broken, just a little off. This year we went after those frictions between your intent and our response. Copying large elements is up to 98% faster, placing large components almost eight times faster, loading the designer, switching pages, locales, seamless items, even typing, the whole internet experience is faster top to bottom, an internal frustration factor tracked by Blaire's cuss counts is down three times this past quarter, good job Blaire. We also focused on your audience, published site rendering up to 43% faster, publishing over 80% faster, what used to take 10-15 minutes now takes less than one, unfortunately I'm drinking fewer pour overs. The best tools are invisible, it's just you and the thing you're making, and more often than not you're working against a deadline where every second counts, we focused on performance and quality of life improvements because Webflow should enable your best work. The features announced today are just the beginning of what's in store this year. Jess, one more announcement. Benjamin, we talked about this, save it for later. They've waited long enough, share it with everyone, I can't think of anyone better than the latest member of the Webflow team, Timothy Ricks. Thank you Ben, I'm excited to join the Webflow team and share one more feature announcement, I love building with components, so I'm thrilled to announce style props are coming to Components later this year, you can change size, color, and even limit the options to create the perfect balance of creative control. That's all we got, Jess back to you. I'm not upset at the interruption, thank you and

welcome Tim. What Ben is too modest to say is he's been working on that feature himself, once he started a bunch of us joined to help get it over the line. A lot of what you've seen today is powered by how agentic development has changed how we deliver internally too, last quarter 100% of our engineering, PM and design teams shipped code to production, pretty cool, even Linda our CEO is shipping regularly, our internal developer productivity team built a custom engineering harness called Flower, it takes all the context, tooling and Webflow technical history to let everyone leverage AI to bring features to life in record time. Watching from the inside it's been wild seeing our team ship so many important updates so quickly, we call our own team Customer Zero, putting all this through the paces before anyone else, and judging by everything shipped this year I'm stoked to keep pushing boundaries with Webflow inside of Webflow. To stay up to date follow our Updates feed, and what would a builder session be without some actual building, if you have quality of life requests visit our UX Papercuts room on the fifth floor, we'll be live building alongside you, members of our product and engineering teams working with you to bring your dreams to life, a great privilege for us as builders. If joining online, scan the QR code to submit ideas or upvote existing ones, authors of the three most upvoted ideas receive Webflow store credit after Webflow Conf. See you there. Thank you.