Should a Webflow request include a screenshot?

Use a picture when similar blocks share a page

A URL names the page. It does not name the third card in a row of six. A screenshot of the current page shows the block you mean. That matters because communication is asynchronous and written only. There are no calls or meetings where you can point at the screen.

Send the picture in the same thread as the request. A file in a side channel is easy to miss, and the hours follow the written queue, not a picture that never landed in it.

Example: the services page has six cards, and you want the second card's heading changed. A shot of that card, with the heading visible, is clearer than 'the blue one.' Name the page in the same note, because a cropped image has no address of its own.

A one-line copy change on a page that has only one heading often needs no picture. Paste the final sentence and the URL. Add the screenshot when the page would otherwise force a guess.

Say whether the picture is the problem or the target

Two kinds of pictures get confused. One shows the site as it is, with the problem marked. The other shows a result you want matched. Write which one you sent, in the same thread as the file.

Example of the current site: 'This is /pricing today. The annual price is wrong. Replace it with the sentence below. Do not restyle the card.'

Example of a target: 'This is the spacing I want on the existing pricing card. Match the gap between the price and the button. Keep the current colors.'

If you do not say which kind it is, a picture of a cleaner layout can be read as a request to rebuild the section. Say what must stay.

A picture of a whole new website, or of a page that does not exist yet, is not a small monthly edit by itself. A new website or a full redesign is a separate project. A picture of one section on a page you already have can be a monthly request, when the note also says what to change and what to leave.

The picture does not replace the words

A screenshot cannot be the only instruction. Keep these in the same note:

• The page address, or the name of the CMS item if you are asking about an item rather than a public URL
• The final copy, when words change
• What done looks like, including a phone if the change is for a small screen

The update brief is the fuller checklist for a site update. This page is only the picture that goes with that brief. The written requests guide is where the note lives. It does not go onto a call.

If the problem shows only on a phone, say so, and send that view. A desktop shot of a menu that fails on a phone sends the work to the wrong width.

Mark the element. An arrow, a box, or a one-line label on the image is enough. An unmarked capture of the whole page makes the next person guess, and a guess can spend the hour on the wrong block.

Do not include a password, an API key, or a visitor's personal details from a form submission. Describe the form problem without pasting someone else's message. You also need the rights to any image you attach as a design target.

Replace an old picture in the same thread

If you send a second screenshot, say that it replaces the first. Two current pictures, with no sentence between them, can spend time on the one you no longer want.

Example: 'Ignore the screenshot from Tuesday. Use the one attached here. The change is only the second card on /services.'

The correction guide is how to replace a queued request before that work starts. Use it when the words changed, not only when the picture did. Name the line to ignore, and put the replacement in the same thread.

A screenshot is the wrong tool for the review after the work is done. Review the result against the written request, then reply publish or hold. The review guide is that check. The picture you attach at the start shows what you asked for. It is not the approval, and it does not approve extra hours.

Keep the file with one written request

Attach the screenshot to the request that names the page and the outcome. Do not send the picture alone and expect the change to be obvious. If a newer shot contradicts the copy in the note, say which one wins.

One request, one current picture, and one outcome is enough for a single edit. A folder of unlabeled exports from a whole site is not a queue. Split the work into the pages you actually want changed, and mark each file with the page it belongs to.

The Webflow retainer is the monthly plan these written requests belong to. The retainer guide explains the ongoing work the hours cover. Use this page when you are deciding whether a picture belongs in the note.