We need a suitable replacement or updated license for Fireworks

Thank you for sharing your personal experience and tool choices.

To clarify, this thread is not about identifying a “better” or more modern replacement, nor about revisiting the merits of one tool versus another. Many of us have explored and adopted alternative tools over the years, each with their own strengths and compromises, depending on context and working habits.

What is being raised here is not whether alternatives exist, but something more concrete: the loss of a very specific way of working that Fireworks supported extremely well for a large number of professionals, and the fact that software that was legally purchased can no longer be used at all, regardless of any migration choices that may have been made.

Alternative tools may work well for some, but they do not address this licensing situation, nor the broader impact on a long standing user community whose workflows were built around Fireworks over many years.

This is the scope of the discussion being raised here.

I would like to express clear and reasoned support for @developer57 ’s message, as it accurately reflects a reality experienced for many years by a large community of Fireworks users.

This message is part of a long series of discussions posted on this forum over the years, all pointing to the same observations and the same practical difficulties that have followed the discontinuation of Fireworks.

This is not about nostalgia for an outdated tool, nor about refusing to adopt modern solutions. It is a much more concrete observation: Fireworks supported unique, fast, and lightweight workflows that have never truly been replaced.

Photopea is often mentioned as an alternative. It is indeed an important piece of today’s ecosystem, especially as a bridge for opening, reviewing, or converting certain file formats (layered PNGs, PSDs). However, Photopea does not replace Fireworks as a tool. It does not reproduce its ergonomics, its hybrid pixel and vector logic, nor the very rich ecosystem of extensions that was central to daily professional use.

Several older but still very relevant articles clearly explain why Photoshop was never designed for fast, iterative web design workflows, I have in mind one of them 50 reasons NOT to use Photoshop for Web Design. This analysis is often echoed, along with comparisons to Illustrator. While Illustrator can indeed cover some vector related use cases, it does not allow direct and fluid work on bitmap elements, which are essential to the workflows described here.

It was precisely this ability to combine, without friction, pixel and vector elements within the same document and the same gesture that made Fireworks unique, and which, to this day, has not found a true equivalent. More recently, an overview Fireworks chaud devant! was published on the Puce & Média blog, revisiting what Fireworks was, what it enabled, and the gap left by its abandonment.

The workflows described by @developer57 are very telling: screenshots, immediate editing, pasting into emails, quick visual drafts created in seconds, saving layered PNGs, and live exchanges with clients. No current Adobe tool offers the same level of simplicity, speed, and flexibility for these use cases.

Today, the most problematic issue is no longer the lack of ongoing development, but the fact that Fireworks has gradually become unusable due to changes in licensing systems, even for users who originally purchased a perpetual license. The deactivation of license verification now prevents any use at all, even at one’s own risk.

Many of us are not asking for renewed support, updates, or Creative Cloud integration. The request is more modest and reasonable : to consider allowing the use of previously purchased installable licenses again, so that users may continue to work with Fireworks knowingly and at their own responsibility.

Failing that, it would be useful to open a clear dialogue with product or marketing managers to seriously discuss what made Fireworks so specific, and what is still missing today in the Adobe ecosystem.

At this stage, and given the recurring nature of these discussions, a relay to teams able to properly assess the real implications of this situation would likely be helpful, when possible.

This community is neither marginal nor backward looking. It is made up of professionals who significantly contributed to making Adobe what it is today, at a time when other choices already existed.

I sincerely hope this thread can move beyond exchanges between frustrated users and finally open a space for discussion with decision makers who can truly understand the scope of what has been lost.

Thank you to @developer57 for articulating these points so clearly.