A screenshot of website content gives Runner AI a visible reference for a storefront request. In a supported desktop browser, use the conversation composer’s Take screenshot action to capture the view you choose. Otherwise, upload a saved image. Add the affected route and the change you want, then review the result in Preview. The image supplies context; it does not send a request or publish a store by itself.
Prepare a screenshot of website content that answers one question
Open the intended store project before adding the reference. Decide whether the image shows a defect to fix or a design detail to discuss. For a defect, reproduce the affected state first: open the route, choose the product option, or expand the menu that causes the problem. For a reference, identify the specific detail you want Runner to consider rather than asking it to copy everything visible.
Include enough of the surrounding page to make the problem understandable. An isolated button may not show which heading it belongs to or which panel overlaps it. Record the route, device or viewport, selected state, and expected result in your message. If the capture comes from an older version, say so; an old reference should not silently become evidence about the current storefront.
Use only material you are allowed to share with the workspace. Remove passwords, payment details, customer records, and unrelated private information before attachment. A public page is not permission to reuse its protected images or wording. Keep verified product facts separate from visual inspiration, because a screenshot cannot establish current prices, inventory, or your store’s policies.
Capture a browser view or attach a saved image
On desktop, open Add beside the conversation composer and choose Take screenshot when the action is available. The browser opens its screen-sharing chooser. Select the intended capture surface, check that it shows the relevant page, and allow capture only when you are comfortable sharing its visible content. Runner captures an image frame and passes it into the message attachment flow; it stops the capture tracks afterward.
This action depends on browser support and a secure context. It is not a promise that every mobile browser or embedded browser can capture a screen. Cancelling or denying the browser permission does not create a screenshot. If the action is missing or capture fails, use your device’s screenshot control and attach the saved image through Upload image, Picture, or Attach, according to the controls shown.
Check the image thumbnail beside the draft and wait for upload progress to finish. Remove the attachment if it shows the wrong tab, an incomplete page, or private information. A browser frame records the selected view, not necessarily the entire scrolling page. If the important detail is below the visible area, prepare that state first or use a permitted saved capture that includes it.
Pair the image with a bounded storefront request
Explain what the screenshot means before choosing Send message. For example, say that a product option panel covers the purchase control in a phone layout, name the affected route, and ask Runner to correct that overlap while preserving product copy and prices. This is an example brief, not a claim that Runner can infer the route, source code, or underlying commerce data from pixels alone.
Separate observations from interpretations. An image can show clipped text, an unexpected gap, or a menu over another element. It cannot show the full sequence that produced the state, prove why shoppers left, or verify a checkout transaction. Add the starting state, action, expected result, and observed result when the request concerns behavior. For an intermittent issue, say when you observed it rather than presenting one frame as a complete diagnosis.
The AI website editor covers focused storefront corrections after you supply the context. Keep the reference and requested outcome in the same conversation so the result can be checked against your brief. Opening the attachment menu or adding an image only prepares the draft. Review both the text and the attachment before sending; do not assume capture itself starts an editing task.
Verify the correction on the working storefront
After Runner finishes the requested work, open the website preview tool and identify the version being displayed. Return to the original route and reproduce the same state. Compare the visible result with the reference, then perform the action that was blocked. A corrected screenshot is not enough if the actual button remains unreachable or the menu still opens on the wrong page.
Use responsive site testing to inspect adjacent device layouts. A phone-specific correction can affect desktop spacing, and a desktop reference does not establish the mobile result. Record whether the route, content, and relevant interaction match the expected behavior. Check connected product, cart, and payment systems separately when the task depends on them.
Keep publication as a separate decision. A screenshot of website content supports discussion and comparison; it does not certify accessibility, performance, purchase readiness, or public deployment. Preview review should establish the bounded change you asked for. Only after the appropriate release checks should you publish and inspect the public store, rather than treating a finished conversation as proof that customers see the revision.
Screenshot of website FAQ
Does Take screenshot capture a whole scrolling website?
The composer action captures an image frame from the browser-selected screen-sharing surface. It should not be treated as an automatic full-page capture or a service that screenshots every route. Prepare the visible state you need first. If your reference requires more page content, use an authorized saved capture and explain which part matters to the request.
What can I do when screen capture is unavailable?
Take the screenshot with your device and upload the saved image using the control Runner shows. Browser support and permission determine whether live capture is offered. Check that the attachment appears beside the draft and finishes uploading. If it does not, follow the displayed file warning and choose a supported image instead of repeatedly requesting browser permission.
Does adding a screenshot send the request or publish the store?
No. Capturing or uploading an image prepares a message attachment. Review the thumbnail and write the requested change before choosing Send message. Inspect the updated storefront afterward. Publication is a separate action with its own checks, and an image attachment does not confirm that the public store changed or that checkout works.
What should accompany a screenshot when I report a problem?
Include the route, version when known, device or viewport, starting state, action, expected result, and observed result. State what must remain unchanged and remove private information from the reference. A screenshot of website content shows one visible state; the accompanying steps let Runner understand the request and let you repeat the same check after a correction.