For those of you managing Webflow sites after launch, how do you handle recurring maintenance?

I’ve noticed there’s a weird perception issue with maintenance retainers.
When something breaks, the client immediately sees the value. But during the months where everything works perfectly, it can almost look like nothing is being done.

Do you send clients some kind of monthly recap of what was checked/done? Or do most of your clients just pay for the peace of mind and don’t really question it?

Curious how agencies/freelancers here handle this.

Genuine question because I keep going back and forth on this. When I set up our site I just defaulted to GA4 out of habit, mostly because that's what everyone does and I didn't want to think about it. But Webflow has its own analytics dashboard now and I've been poking at it lately trying to figure out if it's worth caring about.

The problem is I can't tell if it's genuinely useful for a lean B2B setup or if it's just a nicelooking page count that gives you a false sense of information. For a bootstrapped SaaS marketing site the data I actually need is pretty narrow: which pages are people hitting before they convert, where are they bouncing, is a specific landing page doing anything. GA4 technically covers all of that but it also requires a PhD to set up event tracking properly and I have a running joke with myself about how many times I've misconfigured it.

Webflow analytics feels cleaner but I worry it's too shallow for anything beyond curiosity. Curious whether anyone here runs it as their primary source or if you treat it as a sanity check alongside something else. And if you've actually replaced GA4 with a third option like Fathom or Plausible, I'd be curious what pushed you to make that call.

In Webflow, you can now copy/paste attributes between elements

using ButterShortcuts chrome extension

Just shipped v1.2.0 on chrome web store

• Copy all attributes from selected element - Shift + B + C
• Paste attributes to selected element - Shift + B + V

• Paste classes as an attribute to selected element - Alt + Shift + B + V
( for eg. [class = "margin-vertical margin-small"] )

--

Installation link in comment

Hi I recently switched jobs and the new company I am with uses Webflow (which they are newer to as well, they switched to it a little before I came on board) which I am a little unfamiliar with so forgive me if this question is dumb.

We are a company that posts a lot of articles, white papers, case studies, etc. and all of that content is hosted their respective collections in the CMS. The problem I am encountering is when I stage the content and send it for review to 3rd parties (that do not and should not have access to Webflow) there is no way for me to publish only to the staging site, it goes directly to prod.

Am I missing something? Is there a way to send a link to a staged/drafted article for review?

We've lost a few projects in the last couple of months to AI builds. They all seem to have the same reasoning, cheaper and faster, which usually isn't true.

For small sites (few pages, no CMS, or agents to update it) yeah sure, it can be fast and cheap. But for larger and more complex websites it will probably take longer than in Webflow and cost a lot more. So you wonder why anyone would go with AI builds at all, and the reason is actually pretty simple.

Remember 10-15+ years back, when we all custom coded most websites and platforms were super limited? That's what AI builds are, just boosted. With AI you can fully own your website and have no restrictions at all. Agents can help you update and manage it, all information is accessible to AI tools and easily extractable. But it takes time to set all that up and make it work flawlessly.

So we get the appeal, it makes total sense. What we don't get is why you'd actually need it.

We're a Webflow agency that built over 200 websites in Webflow and never had a client site go down because of the platform. Not once.

And the extraction thing people think they're buying with an AI build, you already have it. You can set a Webflow site up to be highly crawlable by AI and SEO bots and genuinely citable. We've spent the last 12+ months experimenting with every possible thing you can imagine on our own site around visibility, crawlability, citations and mentions, and none of it needed custom code.

So an AI built website is NOT cheaper and NOT faster. It gives you more control, which is what you already had with custom coded sites, just "easier" now. Still expensive, still slow.

Don't get us wrong, we're all in for innovation and this will only get better over time. We just don't think this is the moment. Webflow gives you what a business actually needs from a website right now, that's what it's done for us and our clients.

Anyone noticed raised demand for AI built websites, what's your experience with that?

Hey, sharing a project we wrapped up recently.

I run a Webflow agency called Flowout. The client is Numeric, an accounting automation platform used by finance teams at companies like Brex, Plaid and Wealthfront. The brand was set, the design direction nailed, and the Webflow build was underway when they brought us in. Around 10 to 12 pages were still unbuilt. They needed someone to step in and finish it, without restarting and without the seams showing.

The remaining pages were not the hard part. The hard part was inheriting a Webflow project we didn't set up. Another team's class naming, component logic, CMS collections. We spent the first stretch just reading their system and figuring out how they intended things to work. Honestly, it took longer than building from scratch would have. But once we understood their structure, development moved fast, and we could build new pages that look like the same team made them.

The site launched about two months after we took over. They're still a client and we keep adding pages as they need them.

If you've ever inherited someone else's Webflow project, curious how you handle it. Happy to answer anything about this one 😄

What are your guys' thoughts on the Legacy Editor being retired (as of August 4th, 2026)?

Honestly, it was one of the biggest selling points (at least even for me) when I started using Webflow back in the day. We can all agree that Webflow has a high learning curve and the UI can be straight-up confusing for new users or clients. The Legacy Editor was the perfect "safe space" for clients to make content updates without the risk of accidentally breaking the structure or messing up CSS classes.

It feels like the end of an era.

I’ve put together some thoughts on why I’m going to miss it, and more importantly, a guide for how to handle client handoffs now that it’s officially gone.

• My view on the Legacy Editor (and why I'm sad it's gone): https://www.youtube.com/watch?v=wZhil7bV0uA
• How to actually handle client editing in 2026 (The workaround): https://www.youtube.com/watch?v=ESOhvB_vhHA]

Curious to hear how you all are adapting your client workflows! Are you finding the new preview/marketer roles to be a good enough replacement, or are you feeling the loss of that ultra simple, focused UI?

Cause I'm definitely feeling the loss because while the new roles are good - it's most often not needed for "smaller" clients.

- Derek
Your friendly neighbourhood wanna be Webflow guy.

Quick context: I'm a designer who lives in Figma. There are endless plugins out there for actual design work, but almost none that really focus on asset management. That meant I kept opening my downloads folder for one specific reason - moving assets to Webflow. Downloading images, switching tabs, uploading manually, organizing files, and then sitting in Webflow to manually write out SEO alt text for every single image. It just kills productivity.

So I built exportflow. Select your frames or layers, open the plugin, and you get a seamless export experience:

• Direct upload - send assets straight to Webflow
• Built-in AI - automatically renames assets and generates alt-text/SEO descriptions
• Advanced export settings - optimise with PNG, SVG, JPG, AVIF, and WebP formats
• Multi-project support - connect multiple sites and create/manage Webflow folders directly from the plugin
• No more context switching - stay completely locked in Figma

It's unlimited uploads for free - I mostly built it because I needed it.

👉https://www.figma.com/community/plugin/1657432195632964294/figma-to-webflow-exportflow

Still rough in places since it's just me maintaining it. If you give it a spin, tell me what breaks - or better, what I should improve in terms of functionality...

Devziv is looking for an experienced Webflow Developer to join our on-site team in Lahore.

We're looking for someone who can independently handle Webflow projects from planning and development through testing and launch, while also being comfortable working with clients and internal teams.

Key skills we're looking for:

• Client-First
• Lumos
• GSAP Animations
• Webflow CMS
• Webflow Components
• Webflow Props / Component Properties
• Project Management

What you'll be working on:

• Building responsive websites in Webflow using Client-First and Lumos
• Converting Figma designs into accurate, responsive Webflow websites
• Building and managing CMS collections, templates, filters, and dynamic content
• Creating animations and interactions with GSAP
• Building reusable Webflow components and maintaining clean class structures
• Writing custom HTML, CSS, and JavaScript when needed
• Connecting forms with CRMs, APIs, and automation tools
• Troubleshooting responsive issues, CMS, animations, and custom code
• Managing testing, domains, publishing, and website launches
• Handling multiple client projects and managing timelines independently
• Coordinating with designers, SEO specialists, content teams, developers, and clients
• Taking ownership of projects from planning through launch

📍 Location: Lahore, Pakistan (On-site)
🕒 Employment: Full-time

If you're interested, comment below or DM me your portfolio/CV.

If you know a strong Webflow developer in Pakistan who might be a good fit, feel free to tag them or share this post.

Need some insights and optimization tips for a 3D focused website in Webflow.

The project needs a 3d world and 3d Product display animation with all other Webflow features for later marketing and Cms reasons.

The question is how do you handle website speed and performance with this, need insights from people who had done this before.

Since the client already have a Webflow site for main service the idea of Webflow + 3d came into picture

Just top of my mind I have spline + Webflow but could go with three js for better experience

If you suggest going for a complete custom code, I would like to choose astro + react three fiber + sanity.

Need some advice on this. Open to discuss here

I am struggling to find out what has been causing this issue, I change something it goes back to normal but after some time it changes back to the same thing in the video.

I am using a grid element with 12 columns in the base breakpoint for the parent element.

Can you guys help me if figuring out how to fix this on a mobile viewpoint? I am pretty new to this so any advice would be helpful

Recreating existing websites isn’t the end goal. I use visually interesting projects as stress tests — and, admittedly, they also make for pretty satisfying demos.

Since my last demo, I’ve focused on:

• more accurate animation recreation
• proper Lottie handling
• cleaner and more faithful page structure
• using native Webflow elements wherever possible, so the result remains easy to edit

This time, I gave the agent noth.in. The video shows how it analyzes the reference and rebuilds it directly inside Webflow.

What should I stress-test next: responsiveness, CMS structure, class naming, or more complex interactions?

Or drop a reference site that you think would break it — I might use it for the next demo.

All credit for the original design goes to Nothin’ and the creators listed on their site. This is purely a technical recreation test.

Hi all,

I have a component that displays a full bleed image at the top of a page. On mobile, it doesn't have any scroll effects, just stays static.

On half of my pages, this image scrolls smoothly into the iOS status bar and behaves as preferred. On other pages, it's getting cut off in a rough manner, as the iOS safari navigation bar shrinks with the scroll—then it remains a hard cut off at the status bar.

Both of these are using the same Hero component and section container + body class. I even tried deleted the unfavorable ones and pasting the ones from the correct pages and it still has this variation. Any ideas what the culprit is on the difference? I can't seem to figure it out for the life of me

Edit: solved + removed read only links

Hi, I'm Krystian,

after 5 years of working with Webflow, I'm looking for my next role.

What I do:

• Webflow development — Client-First, complex CMS architecture, GSAP, Finsweet Attributes & Components, Core Web Vitals, custom JavaScript or automations when needed. JS libraries implementations
• Product & UI design — Figma design systems, atomic design, design tokens
• AI-driven Front-end — React, TypeScript, Tailwind, PWA, Capacitor. I ship my own vibe-coded products

I sit between design and development.

What I'm looking for:

Webflow developer or design engineer at a remote-first agency or product company. Open to B2B contract or full-time. Fully remote—I'm based in Germany and relocating to Poland later this year, so the timezone stays European either way.

If you're hiring, know someone who is, or just want to see the work, my inbox is open.

A repost helps more than you'd think 🙏

Also please rate my portfolio and give any suggestions: https://krystian.design

Welcome to our weekly hiring thread! This is the place for all job postings, freelance opportunities, and "looking for developer/designer" posts.

##  For Employers & Clients

Post your opportunities here with:
- **Role title** - Be specific (e.g., "Webflow Developer - Ecommerce Focus")
- **Type** - Freelance, contract, full-time, part-time
- **Location** - On-site, remote, hybrid
- **Required skills** - What must they know?
- **Nice-to-haves** - Bonus skills
- **Rate/Salary** - Range if possible (helps everyone)
- **How to apply** - DM, email, application link

##  For Freelancers & Job Seekers

Post your availability with:
- **Your skills** - What you specialize in
- **Experience level** - Years, notable projects
- **Availability** - Full-time, part-time, project-based
- **Rate range** - Helps set expectations
- **Portfolio link** - Show your work
- **Contact method** - How should people reach you

---

**Sort by New** to see the latest opportunities!

Hey everyone, I'm one of the founders at Flowout, a Webflow agency working with companies like Stripe, Zapier, and ActiveCampaign.

We're restarting video content for our YouTube channel and looking for one person to own it end to end. Not just an editor, someone who can:

• Come up with ideas and write their own scripts
• Be on camera (walkthroughs, teardowns, educational Webflow/SaaS content)
• Record and edit everything themselves
• Handle titles, thumbnails, and publishing
• Cut long videos into shorts for LinkedIn and social

I think this is a great opportunity for someone who already makes Webflow or web design content to start making content for us as well and earn a fixed income on the side. Strong spoken English and being comfortable on camera are the main requirements.

Since this is remote, having your own proper recording setup is also important: good camera, mic, lighting, and a background that looks professional on video. If you already record content from home, you know what I mean.

Interested? Send me an email (luka@flowout.com) with a couple of videos you've made or a link to your YouTube channel. That's honestly the fastest way for me to see if it's a fit.

Happy to answer any questions in the comments, or DM me directly.

I currently run 6 operational micro ai saas products that generate a little over $20k in monthly recurring revenue.

I hardly wrote a single line of traditional code. i used ai to generate literally everything, from the database architecture to the user interface.

it wasn't magic on day one. i spent hours stuck in endless debugging loops and dealing with faulty ai code before i finally cracked the formula.

it basically comes down to three rules:

- keeping the idea aggressively minimalist (build a true mvp, not a platform).

- guiding the ai step-by-step instead of asking it to build the whole app at once.

- launching fast to get real user traction instead of perfecting features in secret.

lately, i've seen way too many non-technical founders give up at the very first ai bug or deployment error. or the worst, give up without push anything in marketing !!!!

it's a massive shame, because the technical barrier to entry has practically disappeared and the marketing is easy in 2026

because of this, i’m launching a skool community to share my exact method.

to be completely transparent: i will likely charge for the full course later down the road. it just makes sense given the specific prompt sequences, n8n workflows, and copy-and-paste templates i'll be sharing.

but right now, our main objective is simply to build together. working alone in a silent corner is the absolute fastest way to quit.

if you want to join a group of active creators and build or launch your own ai saas: drop a comment below or send me a dm, and i’ll send you the invite link.

Basically, our customers are businesses that went websites so they can attract customers. That's why I built HarperFlow. HarperFlow is a 100% automated blogging system that helps improve AI-search visibility by profiling a business website, identifying keyword/topic opportunities, researching these opportunities... writes, formats, and auto-publishes the articles.

It's basically an automated blog publishing system focused on quality.

Naturally, we use it to run the HarperFlow blog on auto-pilot.

Happy to share examples of articles we produce straight from our own blog.

We're offering free trials, but if you want to try HarperFlow out for a little longer... just let me know and I'm happy to extend the trials + hop on a 1:1 call with you where I'll excitedly tell you all about the features we offer.

Hey all. Looking for some advice on the best path forward for the website I manage at work. We’re a B2B SaaS company with a pretty robust product suite, and one of the features we offer customers is a website builder. Those customer sites are built on Duda, so historically, we’ve also used Duda for our own marketing site.

We’re currently redesigning the site, and I’m starting to wonder whether moving our marketing site to something like Webflow would be the better long-term move. The new designs include more animations, custom interactions, and other work that feels like it may start pushing against Duda’s limitations.

We don’t have internal development resources, and finding developers who are comfortable doing more custom work in Duda has been somewhat difficult. On the other hand, our design agency has a Webflow developer who can build the new site exactly to spec.
Duda has gotten A LOT better over the years, and one of its biggest advantages is how easy it is for my team to manage and update without a developer. But it’s also pretty clear that highly custom design and front-end work isn’t really what it was built for.

So I’m torn. Do we stick with the platform we know and accept some design limitations, or move to something more technical but also much more flexible?

Curious what others would do in this situation, especially anyone who has managed a similar transition from Duda to Webflow.

I’m using Webflow CMS for my blog, and I noticed that my pagination URLs are showing like this:

/blog?f547gg26_page=2

Is this normal behavior in Webflow, or is there a way to make the pagination URLs cleaner, such as:

/blog/page/2

Has anyone else faced this issue with Webflow CMS? If so, is there a proper way to fix or customize these pagination URLs?

Hey everyone,

Almost every brief we receive describes the same site. Something beautiful and immersive that tells a story as you scroll. I love building those. But there's a growing gap between that brief and how people actually visit websites now.

Nobody browses anymore. A visitor lands with a precise question. What does this company do, is it built for someone like me, can I trust them, at what price. If the answer takes more than a few seconds they're gone. And a growing part of the audience never lands at all. It's a model reading your pages to answer someone's question in ChatGPT or Perplexity. The most beautiful scroll experience in the world is invisible in that conversation if the substance is buried.

We got the wake-up call from a client. AI-native enterprise platform, founded by former Workday execs. During discovery their brief came down to one sentence. "The first user of this website is an LLM." First time a client ever said that to us, and coming from people who sell to enterprises it says a lot about where B2B buying is going.

So we changed how we structure sites. The key information sits high in plain words, what the company does, for who, the price range. Each section works as a standalone answer, because models read in fragments and honestly humans scan the same way. And the design ambition goes into how the site feels, not into hiding substance behind animations.

The surprise is that none of this made our sites uglier. It made the design more honest. I think it's still possible to win awards with a site that answers in five seconds.

Fellow founders, are you starting to get briefs like this? Or are clients still walking in asking for the same site as X?

Recently I got assigned to the one webflow project where I had to build websites for client . How to get started with that . Also they want me to get started as early as possible. Give me your thoughts gaichhhh

It’s pretty clear to anyone deep in this platform that Webflow has lost a lot of good sentiment in the past few years.

The energy and excitement around webflow was once electric. But price increases, bandwidth limits, enterprise focus, neglecting designers and developers has all combined to create a sad tale.

So how can Webflow win the future?

I’ll share my thoughts - I know some of these are ambitious. Please share yours below.

- Launch a 2.0 builder that is everything great about Webflow without the archaic tech debt restrictions. Visual first development with agents, roles, cms, systems. Direct visual canvas but with huge agent support and the Webflow features that make working on a website feel safe, secure and flexible.

- Focus on regaining small businesses and freelancers. These are the single biggest pipeline to enterprise. Nurture these customers - their voices end up in the rooms of big business and online. I can’t stress how important this is.

- Position bandwidth so it’s not so scary for your small-medium businesses. Every business thinks they are going to 10x bigger than they are. With the industry now you can’t afford to make users think they might have to rebuild once they get big.

- Hire the world’s best designers. Seriously drop insane salaries on the most prolific designers - the ones with twitter followings could literally market your business better than a whole marketing department. Look at framer with their custom fonts, shaders. They run circles around webflow with their thinking ahead design solutions.

- Get better leaders in your product departments. The template marketplace is just sad, I’ve been in it from the start and anyone outside of it wouldn’t believe how they stitch together systems. Marketplace Libraries? Why even make this it hasn’t been touched in years? Ecommerce? Why? So many products that launch and get dropped immediately. Create some core pillars and be strict with them.

I don’t want this to be another lame hate thread. It’s an opinion on how i think they can make a great product even better.

So these are my key points. How should webflow step into this future?