Last verified: November 2, 2026
What You Can Now Do
Context Memo now lets you click to expand screenshots within Pages for a larger, more detailed view. Any image you place in a Pages builder block becomes clickable for your readers, opening at full size in an overlay on the same page. That changes what you can reasonably put in a page. Product screenshots, dashboard views, annotated workflow diagrams, and slide exports no longer need to be simplified down to whatever stays legible at inline width. You can publish the real artifact and let the reader open it.
Where It Is in Context Memo
The image-expand component lives in the Pages builder. Open any page in Pages, add or edit an image block, and the expand behavior applies to the rendered page automatically. To see it working before you build anything, check the operating model deck that now ships as onboarding content in your workspace. It was seeded specifically to demonstrate expandable screenshots in a real published page rather than a help article.
How to Use It
- Open the seeded operating model deck from your onboarding content in Pages. Click any screenshot in it. The image opens at full size in an overlay and the page stays where it was, so you can confirm the reader experience before you commit to a layout.
- Open the page you want to add a screenshot to and select the image block in the Pages builder. Upload the screenshot at its native resolution, not a downscaled version. The inline render sizes itself to the column; the expanded view uses the file you uploaded.
- Preview the page and click the image. If text inside the screenshot is unreadable at full size, the source file is too small. Replace it and preview again.
- Publish the page to your own domain. The expand behavior carries through to the live page, so readers on your domain get the same full-size view, and the crawlers hitting that page see the surrounding text you wrote around the image.
- Check the page in your citation tracking a few days after publishing to see whether the memo or page is being scanned and cited. Images are not what models cite; the text around them is. Use the screenshot to hold a human reader on the page, and keep the caption and body copy specific enough to stand alone.
Why We Built It
Customers can now see screenshot details clearly without leaving the page or opening external tools. Before this shipped, a screenshot in a page was a thumbnail with a promise. Readers who needed to see a dashboard, a report view, or a workflow diagram had to right-click and open the file in a new tab, or the author had to skip the image entirely and describe it in prose. Both outcomes cost something: the first sent a reader away from a page built to keep them there, the second stripped out the visual proof that makes a page credible to a buyer doing diligence.
That matters more for Pages than it would elsewhere in the product. Pages publish on your domain, which means they carry your authority and they are what a buyer or a model encounters when it looks for evidence about your product. Evidence you can't read is not evidence.
What It Does Not Do Yet
The component handles expansion, not image production. A few limits worth planning around:
- Resolution is on you. There is no upscaling. If you upload a compressed screenshot, the expanded view shows a larger compressed screenshot. Capture at 2x where your tooling allows it.
- No annotation, cropping, or markup inside the builder. Arrows, highlights, and redactions need to be applied in your own image tooling before upload. For anything with customer names, account IDs, or revenue figures in the frame, redact before it reaches the builder, not after.
- No galleries or multi-image sequences. Each image expands on its own. A step-by-step sequence still means separate image blocks in order.
- Pages is not a CMS or a replacement for your marketing site. Those platforms carry functionality Pages does not, and we are not pretending otherwise. Pages exists to publish citation-grade content on your domain fast; treat it as that, and keep your primary site where it is.
If you have screenshots sitting in a Notion doc or a slide deck because they never survived being shrunk into a page, this is the week to move them. Start with the pages your buyers reach late in evaluation, where the detail in a dashboard view does actual work.
Changelog
November 2, 2026
QR Code SVG Export for Pages. You can now opt in to receive QR code SVGs when retrieving page data via the API, enabling you to embed scannable codes in print materials and external documents without additional requests.
