The most striking detail in FreeHand’s history is that Adobe encountered the application through two separate acquisitions.
In the first, FreeHand had to leave the combined business. In the second, it stayed.
That makes a powerful opening to the larger FreeHand story. It also creates a temptation to simplify regulatory history into a permanent prohibition followed by an unexplained exception. The available documents call for a more careful account.
Why FreeHand was involved in the Aldus transaction
Adobe made Illustrator. Aldus marketed FreeHand under its arrangement with the developer, Altsys. Acquiring Aldus therefore brought competing professional illustration products into the same transaction.
The FTC’s later summary of the 1994 consent order explains the competitive concern and the remedy: divest FreeHand to Altsys.
The market context matters. The proceedings concerned professional illustration software for the relevant Macintosh systems. It is not accurate to expand that into a statement that only two drawing programs of any kind existed anywhere.
The remedy preserved an independent competitor
A divestiture changes ownership so that competition can continue outside the merged firm. In this case, FreeHand returned to the company that had developed it.
For a reader interested in design history, this has an immediate implication: FreeHand was consequential enough that its independent future became part of the conditions surrounding a major software transaction.
It does not prove that regulators preferred FreeHand’s tools, interface, or output. Competition policy and product criticism answer different questions. A rival can matter even when users disagree strongly about its merits.
A later petition complicates the shorthand
The FTC announced in December 1995 that Adobe had petitioned to remove a prior-approval obligation from the order. The announcement connected that request to a broader policy change in how the agency handled such provisions.
A petition is not its own approval. The announcement alone does not establish the final disposition. It does establish that the original regulatory arrangement had a procedural history after 1994.
For that reason, this article does not claim that Adobe was permanently barred from acquiring FreeHand, nor that the 2005 transaction violated the earlier order. Those assertions require more than placing two acquisition dates next to each other.
The unresolved petition detail does not prevent describing the verified ownership sequence. It does limit the causal explanation we should attach to it.
Adobe acquired Macromedia in December 2005
Adobe’s SEC filing records that Macromedia became its wholly owned subsidiary on December 3, 2005.
FreeHand was then part of Macromedia. The acquisition put it within the same company as Illustrator. That is the second event at the center of this story.
The distinction between a transaction’s announcement, legal completion, and the announcement of a product decision is worth preserving. They are different milestones. Using a single “Adobe killed FreeHand in 2005” date obscures the sequence.
Development decisions followed a separate timeline
FreeHand MX had already gone several years without a new major release when Adobe announced in May 2007 that further feature and compatibility updates were not planned. Adobe also said sales and support would continue under its policies. The contemporary announcement is more precise than the shorthand obituary.
Those facts can support criticism of the outcome without establishing a particular legal conclusion. Product consolidation may frustrate users, but a historical article should distinguish that frustration from an adjudicated violation.
The later Free FreeHand litigation made its own allegations and produced its own procedural record. It should not be treated as the FTC proceeding continuing under another name.
What this history means for designers
A software choice is partly an investment in habits, documents, and relationships. The product can remain familiar while the business behind it changes direction.
When an application disappears, a user loses more than access to the next set of tools. Training material ages. Compatibility erodes. An archive becomes harder to recover. Collaborators gradually move elsewhere.
Those consequences explain why preserving competition can matter to users in practical terms. They also explain why a revival needs a preservation strategy. Openly inspectable artwork, dependable exports, and clear limits can reduce the cost of a future transition even when they cannot guarantee a product’s survival.
This is an editorial lesson drawn from the history, not a legal conclusion from the FTC order.
The most useful question for Backhand is not whether history can be reversed. It is how to build a new application whose usefulness does not depend on users mistaking a file format, a brand, or a roadmap for a permanent guarantee.
