Webflow Editor Tutorial for Clients: Update Your Own Site

You update a Webflow site yourself in Edit mode, the simplified content view that opens on top of your live pages, and the whole job is four steps: open the page, change the element, check it, publish. Text and image edits on a normal page save automatically, while CMS items such as blog posts or team members save as drafts until you press Publish now. Edit mode has no controls for layout, spacing or fonts, which is where a developer comes back in.

The four steps in full:

• Open the page you want to change and add ?update to its URL, or open the site from your Webflow dashboard.
• Select the element, click the Edit icon above it, then pick the pencil for text or the landscape icon for an image.
• Read the change back on the Edit mode canvas, and use the eye icon to preview a Collection item before it goes out.
• Publish to your live domain, then open the public URL to confirm it is really there.

I build and hand over Webflow sites for agencies and their end clients, so the rest of this guide follows the questions that actually come up in the first month after launch rather than a feature list.

Where do you log in to edit a Webflow site?

You open a Webflow site for editing in two places: the Webflow dashboard, where you hover over the site and click Open in Webflow, or the live site itself, by adding ?update to the end of any page URL, as in www.my-website.com/page1?update. A Webflow site has no separate login page of its own, which is why clients coming from WordPress often cannot find the way in.

The ?update shortcut has been available since January 15, 2026 and works for every Workspace member and every user with a client seat. On the handovers I run, ?update is the one thing I ask the client to bookmark, because it lands them on the exact page they were already looking at instead of making them hunt through a site list.

The legacy Webflow Editor that older tutorials still show has been retired, so a guide that tells you to visit yoursite.com/?edit is describing a tool that no longer exists. The access and permission side of that change is covered in my guide to the Webflow client handoff.

Why can you change the words on a Webflow page but not the layout?

Webflow Edit mode gives you the content layer of a site and holds back the design layer, because Webflow styling is a system of reusable classes rather than per-page formatting. One heading on one page usually shares its class with every other heading of that rank on the site, so a single nudge to its size or spacing would move all of them at once. The rule I give clients is short: if a change alters what the page says, it is yours; if it alters how the page is built, it comes to me.

Some elements will not respond to a click at all, because whoever built the site locked them through Editing permissions, and anything bound to the CMS inside a Collection list is locked that way by default. An unresponsive element is usually deliberate rather than broken, and the detail of which seat type may touch what sits in my Webflow client handoff guide.

Which Webflow edits need a publish, and which save automatically?

Page text and images save automatically as you edit them and then need a site publish to reach visitors, while anything you change in the CMS tab saves as a draft and needs Publish now. Page settings such as the SEO title behave like page content: saved immediately, invisible to search engines until the page is published again.

Client task	Where it lives in Edit mode	Does it need a publish?
Rewrite a heading, paragraph or button label	Edit icon on the page canvas	Saves automatically, publish to go live
Swap a photo or a video	Landscape icon on the page canvas	Saves automatically, publish to go live
Change the URL behind a link or button	Link icon on the page canvas	Saves automatically, publish to go live
Add or edit a blog post, case study or team member	CMS tab	Saves as a draft, needs Publish now
Edit a page's SEO title or meta description	Page settings	Needs a publish before search engines see it

How do you edit text and swap an image on a live page?

Editing text or swapping an image on a live Webflow page takes the same short sequence every time: click the element, click the Edit icon that appears above it, then pick the control for what you are changing. Webflow's own wording for the sequence is "Select an editable element", "Click the Edit icon above the element", then "Make your edits (e.g., enter new copy, replace an image, change the URL)".

1. Click the element on the page, which outlines it and puts an Edit icon above it.
2. Click that Edit icon and choose the control for the job: "Pencil for text", "Link for hyperlink settings", "Landscape for assets" and "Gear for image settings".
3. For text, type the new copy, then use the formatting controls to "select text and format it (e.g., bold, italicize, wrap with span)".
4. For an image, open the landscape icon, upload the new file or pick an existing one from the Assets panel, and write alt text for it in the same visit.
5. Read the sentence or the image back on the canvas, since static page content changes are saved automatically the moment you make them.

Export a photo at the width it is actually displayed at before you upload it. The Webflow Assets panel caps uploads at 4MB for images and 10MB for documents and audio files, and asks for filenames of 100 characters or less including the extension. A photo straight off a phone is routinely larger than that image ceiling, so the upload either fails outright or lands as the heaviest thing on the page. My notes on preparing a Figma file for a Webflow build cover getting image exports right before they reach Webflow at all.

How do you add a new blog post or CMS item yourself?

You add a new blog post, case study, testimonial or team member from the CMS tab in Edit mode, and nothing you type there is public until you publish it. Repeating content of that kind lives in Collection items, and the CMS tab lists every Collection on the site, so the job is a matter of opening the right Collection and clicking New. Webflow's documented path runs as follows.

1. "Go to the CMS tab" in Edit mode.
2. "Click the Collection to view its Collection items", for example Blog Posts.
3. "Click New to create a new Collection item or click an existing Collection item to edit it".
4. Fill the fields, remembering that "changes are automatically saved in draft state" rather than published.
5. "Optionally, click the Eye icon to preview the page or click Publish now to make the changes live".

An empty required field is the usual reason a new Collection item refuses to save, because required fields are set when the Collection is built and cannot be changed from Edit mode. When a client tells me a new post will not save, the first thing I check is whether a required image or summary field is still blank.

Why does replacing an image in the Assets panel break old links?

Replacing an asset in the Webflow Assets panel changes that asset's URL, so every link already pointing at the old file stops resolving. Webflow's documented behaviour is that a replaced asset "will be updated everywhere it's used on your site", that "replacing an asset also changes the asset link (i.e., the URL)", and that "any direct links to the asset's URL, whether on your site or external sites, will need to be updated manually". A replaced logo therefore updates every page at once, which is usually what you wanted, while a replaced PDF quietly breaks the download link in every newsletter you have already sent. When a client asks me to update a price list that went out by email, the rule I apply is to upload the new file as a separate asset and repoint the on-page link, never to replace the original.

Why do your changes not appear on the live site?

Webflow changes do not reach visitors until they are published to the live domain, and publishing is both explicit and per-domain. Static page edits save as you type but still need a publish, while Collection item edits sit in draft state until you click Publish now. Publishing is its own deliberate action: click Publish, tick the domains you want, then click "Publish to selected domains", as the Webflow publishing documentation sets out. A Webflow site normally has both a webflow.io staging address and your real domain, so a change that shows on one and not the other went to the wrong target. When I get a message saying an edit vanished, staging-only publishing is the first thing I check.

When a Webflow edit is not showing up, work down this list in order:

1. Confirm the edit was made in Edit mode on the site itself rather than in a comment or a shared document.
2. Check whether the element is a Collection item, which stays in draft state until it is published.
3. Open the publish menu and confirm your custom domain was ticked, not only the webflow.io staging address.
4. Reload the public URL in a private window, which rules out your own browser cache.
5. Check that the page itself is published, since a brand new page needs a publish of its own before any URL resolves.

A Webflow change that survives all five of those checks and is still invisible is worth escalating to whoever maintains the site, because the cause at that point is usually a redirect or a page setting rather than the edit. A Publish button that is missing or inactive means publishing was not enabled for your seat, and that setting lives with whoever owns the Workspace.

What goes wrong when clients edit their own Webflow site?

Pasting styled text out of Word, editing a heading that lives inside a shared component, uploading a photo straight off a phone, replacing an asset that is already linked from elsewhere, and leaving a Collection item in draft are the editing mistakes behind nearly every emergency message I get from a client after launch. Each one has a cheap fix if you catch it early. Webflow adds a quieter risk when several people work at once: multiple team members can edit a site at the same time, and where two people change the same content, "the last edits win", so agree who edits what before anyone opens Edit mode.

Which edits should you still send to your developer?

Send your developer anything that changes the structure, the styling or the addressing of a page, because those edits are either blocked in Edit mode or carry side effects you cannot see from the canvas. The requests I ask clients to send over rather than attempt are these:

• Page slugs and page names, which break existing links when they change.
• New sections, new pages or a new page template.
• Spacing, colour, font size and any other styling change.
• New CMS Collections, or new fields inside an existing Collection.
• Custom code, tracking scripts and analytics tags.
• Anything involving a form's settings or where its submissions are sent.

Page slugs matter more than clients expect, since changing one breaks every existing link to that page unless a redirect is set up at the same time. On the projects I lead, the division I hand over is that the client owns words, pictures and CMS entries, and the developer owns everything deciding where those sit and what they look like. If you are unsure which side an edit falls on, write it up as feedback instead of guessing, using the approach in my guide to giving design feedback to developers.

Agency-delivered builds add one more layer, and the ownership and access arrangements behind the split are set out in my white label Webflow workflow. The SEO title and meta description fields you can edit yourself are explained in my guide to the Webflow meta description and title tag.

Want a walkthrough of Edit mode on your own site?

I run a free 15-minute call where we open your site in Edit mode together, bookmark the ?update link for the pages you change most, and work out which edits are safe for your team and which should come to a developer. You leave with that split written down and the publish routine confirmed on your real domain, so the next content change does not need anyone else. Book the 15-minute Edit mode walkthrough.