A New Chapter for Avada

It’s been a while since our last roadmap update in October 2025, and we know many of you have been wondering what’s next. Before anything else, we want to acknowledge that directly. The gap in communication has been longer than we would have liked, and longer than you deserved.

We understand that silence can be unsettling, especially when you’re relying on a product for your day-to-day work or waiting on news that matters to your plans. That was not the experience we wanted to give you, and we take responsibility for it.

While we’ll go into more detail throughout this post, the short version is that we’ve spent the past few months carefully evaluating the future direction of the Avada ecosystem and ensuring we take the right long-term path for both our products and our users.

Part of that process also coincided with significant platform and business-model changes introduced by Envato that directly impact authors and long-term product sustainability. As those changes unfolded, it became increasingly important for us to take the time to evaluate not just the technical roadmap ahead but also how we can continue to deliver the level of innovation, support, and long-term commitment that Avada users expect from us. Because of that, we felt it was important not to rush into further roadmap updates or announcements until we had a clear, confident direction for the platform and the ecosystem as a whole.

Throughout that time, we know many of you have been eagerly following the progress of what we previously introduced as Avada 8, looking forward to its release and the improvements we’ve been previewing along the way. We understand this news will land differently depending on what you’ve been waiting for, and we want to acknowledge that. Whether you’re excited about what’s next or you simply rely on Avada every day and want to know it’s in good hands, we hear you. This post is our honest account of where things stand and where we’re headed.

What started as a new framework steadily evolved into something much broader in scope, and the story of how that happened is worth telling properly.

Over the past two years, we’ve been working intensively on what we initially introduced as Avada 8, a completely reimagined experience with a new UI, improved UX, enhanced performance, and a modernized data structure. Along the way, we’ve shared glimpses of that journey through our roadmap updates.

As the project matured, we saw how modern design and development patterns were evolving across the industry. New ways of building, structuring content, and creating workflows were emerging, and the possibilities in web creation were expanding in directions that opened up genuinely exciting opportunities. Rather than lock ourselves into an earlier approach, we deliberately raised the bar.

That meant revisiting parts of the foundation we had already built, not because the original direction was wrong, but because we saw a better path and wanted to take it. We didn’t just want to follow those trends. We wanted to implement them in a way that meets the level of quality and refinement you expect from Avada. Doing that properly took time.

And as the scope grew, so did the depth of the decisions in front of us. Each time we pushed further into what Avada 8 was becoming, it became clearer that the changes we were making were not just additive. They were foundational. The kind of changes that, if done right, would allow us to build things in the future that would simply not be possible on the architecture we had been working within before. And if done hastily, it would result in exactly the kind of fragmented, patchwork system that creates more problems than it solves.

At the same time, we made a conscious decision: we didn’t want to rush out a major release built on partially adapted foundations, only to spend the following months or even years refining, restructuring, or correcting underlying systems. Many of the improvements we had been working on require bigger changes to the core framework and codebase. Without taking the time to implement them properly from the ground up, the result could easily have become a system that limits what we can build on top of it for years to come. Instead, we chose to invest more time upfront to ensure a solid, future-proof foundation.

As that scope grew, another challenge became increasingly clear. The depth of architectural change we were pursuing pushed hard against the constraints of backward compatibility. Supporting the full weight of the existing Avada structure while simultaneously building something genuinely new created a tension that could not simply be engineered away. At a certain point, trying to do both well meant doing neither well. The more we tried to preserve full compatibility with everything that came before, the more it constrained what we could build for the future.

Over time, it became clear that the scale of what we were building could not be realistically integrated into the existing Avada product structure without fundamentally altering the experience that many users know, love, and rely on today.

With that in mind, as the scope and long-term vision evolved, we recognized that a different approach would ultimately yield the best result for everyone.

To be direct: Avada 8, as it was originally conceived and communicated, will not be released. What began as Avada 8 grew so significantly in scope and ambition that it outgrew the boundaries of a traditional major version update. Trying to ship it as one would have meant compromising on the very things that made it worth building. We’re not willing to do that, and we don’t think you would want us to either.

Instead, that vision has evolved into something broader: a new, dedicated platform built around a modernized interface, reimagined workflows, improved performance, deeper flexibility, AI-powered capabilities, and an entirely new architectural foundation designed for long-term evolution.

Rather than trying to force all those changes into the existing Avada product structure, we decided to allow that vision to grow into its own dedicated platform: Avada One.

The name is deliberate. Avada has always been built around the idea of giving website creators everything they need in one place. With Avada One, that idea takes on a whole new meaning. One product. One account to connect and manage all your sites. One platform that, over time, will bring together design, content, AI, and marketing capabilities in a way never before possible. Built for everything modern web creation requires, and built to make managing it all significantly simpler.

That is the foundation we are building toward. And with Avada One, we are building it from the ground up.

Avada One represents the next generation of the Avada experience, built from the ground up on a new architectural foundation and designed around the workflows, expectations, and possibilities of modern web creation. And here we want to set expectations clearly from the start, because we think that matters more than building anticipation.

Avada One will not arrive as the full product we have been previewing over time. The initial release is a foundation. From that foundation, the experience will grow into something that simply would not have been possible within the current Avada framework. It establishes the new architecture, core systems, and ways of working that everything else will be built on. Much of what you know from Avada will still feel familiar in that first version, and that is intentional. But what is different under the surface matters enormously for where Avada One can go from here, even if not all of that is immediately visible in the early experience.

From launch, our plan is to move at pace. Regular feature updates will build progressively and bring Avada One closer to the full vision we have been working toward. The destination remains the same as what we have been previewing. The path there is incremental and deliberate, because we believe that is the right way to build something that will genuinely last.

At the same time, this approach allows us to protect and preserve what many users already love about Avada today. And that distinction is important.

The original Avada will continue to be sold on ThemeForest with the same licensing model, ongoing updates, support, fixes, and continued development. Nothing about your current setup has changed.

For users who are excited about the future-facing vision we’ve been building toward, Avada One will open the door to that next-generation experience. For users who love the current Avada experience exactly as it is, that path remains fully supported. You do not need both; each is designed for a different direction, and the choice is entirely yours.

Avada One will be sold directly through avada.com and will follow a subscription-based model designed to support the long-term sustainability, infrastructure, and ongoing innovation behind the platform.

While the full scope of the initial release will be shaped by what we can deliver to the standard Avada One deserves, some things are already certain.​

Starting with something that will make a noticeable difference from day one: Avada One ships as a single, unified package. No more separate Avada Core and Avada Builder plugins to install, manage, or keep in sync. One product, one update, one place to manage everything.

Product registration is also getting a meaningful overhaul. Instead of managing purchase codes, you will connect your website directly to your My Avada account using a simple OAuth login. From there, you can see and manage all connected sites in one place, making it significantly easier to keep track of your projects and licenses.

On the design side, Avada One introduces a completely new dashboard experience and a comprehensive overhaul of global color handling across your projects. On the AI side, the platform will include practical, integrated tools for image creation, image adjustment, and text generation, as well as an AI-powered help center to support you as you work.

These are the starting points. Beyond everything we have already been building toward and previewing as part of the Avada vision, we are also excited to share that marketing and sales tools will be coming to Avada One as a dedicated addition. Bringing those capabilities directly into the platform has been part of our planning alongside the core product, and it is one of the things we are most looking forward to introducing as Avada One grows. More on that soon.

The original Avada and Avada One are designed to coexist long-term, serving different needs and different directions:

The naming distinction and separation allows both products to grow as intended, without one limiting the other. And it allows you to choose the experience that best fits your workflow, projects, and future needs.

We know that one of the first questions many of you will have is how the original Avada and Avada One will work together in practice, especially regarding existing websites, workflows, and long-term compatibility.

At the beginning of this journey, Avada One will offer compatibility with current Avada content and workflows, for sites that have kept up with Avada’s recent updates and are using its current set of tools. If you’ve been keeping pace with Avada’s evolution, you’ll be able to explore and transition smoothly, without having to rebuild or change everything you already have in place.

If your site relies on older approaches or has not been updated in some time, some content may not carry over directly. This is a good moment to review and modernise your setup, not only to take advantage of what current Avada already offers, but to make any future move to Avada One as straightforward as possible.

At the same time, it’s important to understand that Avada and Avada One are built on different foundations and will evolve as separate products over time. As Avada One continues to develop independently, a fully seamless long-term upgrade path between the two may become less practical. But that’s a bridge for the future; there is no requirement or deadline to move, and you can continue using Avada exactly as you do today for as long as you choose.

And that’s also what makes this exciting. Avada One is not just a continuation, it’s the beginning of a new chapter. A platform where we can explore new ideas, introduce new workflows, and build the future of web creation in a more flexible and modern way.

We want to invite you to be part of that journey from the very beginning. Your feedback, your use cases, and your experience will play a key role in shaping where Avada One goes next.

Avada One will be offered as a subscription-based product, and this decision was not made lightly. It also reflects the realities of recent changes to Envato’s author ecosystem, as outlined earlier in this post, further reinforcing the need for a sustainable, long-term platform.

The scale of innovation, infrastructure, AI-powered capabilities, long-term maintenance, and continuous development behind Avada One requires a model different from the traditional one-time licensing structure. Most importantly, this model allows us to build Avada One for the long term and continue investing heavily in development, support, and the platform’s future.

It also gives us the flexibility to offer more scalable, cost-efficient options for agencies, freelancers, and multi-site users, including bundled licensing that makes managing multiple projects significantly easier and more economical.

In addition, Avada One will be available in different subscription tiers, including options both with and without built-in AI credits, allowing users to choose the setup that best fits their workflow and needs.

We know pricing and subscription tiers will be top of mind for many of you, along with questions around how access and licensing will work between Avada and Avada One, and whether existing Avada customers will be recognized in some way. What we can say is that we’re aiming for pricing that reflects the value Avada One delivers while remaining accessible, and structured to feel like a familiar, reasonable step for users who are already part of the Avada ecosystem. Everything is currently being worked through in detail, and we will share full information as soon as we get closer to launch and everything is ready to be communicated properly.

Alongside pricing and subscription details, another question we know many of you will have is timing. At this stage, we cannot share a specific release date yet. We can say we aim to launch this summer. Avada One is well underway, with a significant portion of the underlying work and core architecture in place.

Rather than being an early-stage concept, Avada One is now transitioning into its first release phase. Many parts are already complete, and the current focus is on refining, stabilizing, and bringing everything together into a cohesive first version. From launch, the plan is to move at pace, with regular feature updates that build progressively toward the full experience we have been working toward.

We are intentionally avoiding committing to a firm date too early to ensure what we announce is something we can fully stand behind. As soon as we are in a position to share a clear launch timeline, we will communicate it directly.

To help summarize everything covered in this update, here are the most important points:

What we are building with Avada One marks the beginning of a new chapter for the Avada ecosystem, not a single release moment, but an ongoing evolution of ideas, workflows, and capabilities that will continue to grow over time.

We also want to say plainly: we know this journey has asked for a lot of patience from you. The wait has been longer than any of us planned for, and the road has taken turns we didn’t anticipate. We don’t take that lightly, and we are committed to showing through our actions going forward that the decisions we’ve made were made with your long-term experience in mind.

Avada Classic itself remains exactly as you know it today: a stable, trusted product that continues to receive updates, improvements, and long-term support throughout its lifecycle. And Avada One represents the next generation of thinking, a platform you can grow into at your own pace, when and if it makes sense for you.

If you choose to explore Avada One when it becomes available, you will be joining us at the very start of that journey, helping shape it through real-world use, feedback, and experience. And if you continue working with Avada Classic as it is today, nothing changes for you.

Either way, this is not a replacement for what came before. It is an expansion of what is possible. We are looking forward to building this next phase together with you.