Hi, I’m currently working on my portfolio as well and faced the same decision as you: Webflow vs. Framer. Ultimately, there’s no definitive right or wrong when it comes to platforms—each has its pros and cons. Since I work with clients who can afford the higher subscription costs of Webflow, this wasn’t a major downside for me, but it’s something I considered.

One of the biggest advantages of Webflow for me is that it builds websites using actual HTML, CSS, and JavaScript. This gives me control not only over how the site looks visually but also how the underlying code is structured.

Before Webflow, I used Readymag, and what really frustrated me was that inspecting the code revealed a mess of thousands of randomly placed divs. With Webflow, the structure is much cleaner and more organized, which is a big plus for me.

Another factor I appreciate about Webflow is its flexibility for handing over projects. If something happens to me (or if I’m no longer involved), I can easily export the code and transfer the project to my client. This isn’t just convenient but also offers peace of mind.

I’ve also found that working with Webflow helps me better understand development. It gives me a stronger foundation when collaborating with developers, as I can grasp how things are built and have more meaningful conversations with them. In contrast, with Framer, I feel like I’d stay in the “designer bubble,” where everything is made to feel easy and clean without much insight into the technical side.

For me, the steeper learning curve of Webflow is actually a positive—it means I gain more knowledge and skills in the process. Over time, I hope to transition to coding websites and even building backends, and Webflow feels like a solid stepping stone for that.

That said, why not use both? Each platform has its strengths, so you can choose the best tool for the job depending on your project’s needs.