In 1994, Adobe’s acquisition of Aldus brought two competing illustration programs into the same corporate transaction. Adobe had Illustrator. Aldus marketed FreeHand. The Federal Trade Commission required FreeHand to be divested to its developer, Altsys, preserving an independent competitor. Eleven years later, Adobe acquired Macromedia, which by then owned FreeHand. This time, the application stayed with Adobe. The FTC’s account and Adobe’s acquisition filing establish that unusual sequence.
In May 2007, Adobe said FreeHand would receive no further feature releases or updates for new operating systems and hardware. That ended its development future, although Adobe said it would continue selling and supporting MX under its existing policies. The announcement is still available.
That answers what happened to Macromedia FreeHand. It does not quite explain why people still care.
For that, you need to look at the work the program held together: drawing, lettering, layouts, alternate designs, placed images, and all the little production changes that turn an attractive composition into a finished job.
A place to work, rather than a single drawing surface
FreeHand was a vector graphics application. Its shapes and curves could be scaled, edited, recolored, and combined without treating every mark as a collection of pixels. But that definition understates the experience.
A designer could keep several differently sized pages in one document. A logo exploration could sit beside a business card and a letterhead. Type could follow a path, flow through linked blocks, or participate in a larger composition. A closed shape could contain other artwork without destroying the portions outside its boundary. Repeated visual attributes could be found and changed across the document.
These were documented operations, not features reconstructed from affectionate memories. Macromedia’s Using FreeHand MX manual covers pages and master pages in chapter 2, object operations in chapter 4, typography in chapter 8, and reusable assets in chapter 9.
Imagine preparing a small restaurant identity. You are still changing the symbol, testing its lettering, fitting it into a menu, and adapting it to a narrow sign. Those activities overlap. They do not arrive in a tidy sequence labeled illustration, then layout, then production.
FreeHand gave that overlapping work a common home. Its appeal is easier to understand when you picture the whole desk rather than one tool on it.
Why the ownership story matters
The FTC intervention is compelling because it makes clear that FreeHand was a consequential competitor. It was not merely an obscure alternative that Adobe happened to acquire.
The regulatory story also needs care. The 1994 proceedings concerned a specifically defined market, and the later history includes a petition to change a prior-approval requirement. It would be misleading to turn the episode into a claim that Adobe defied a permanent ban in 2005. The two transactions occurred at different times and under different circumstances.
The dedicated FTC article follows those distinctions. For the wider history, the important result is straightforward: FreeHand continued under a different owner after the Aldus transaction, then eventually returned to Adobe through Macromedia.
The Macromedia version of a designer’s desk
The MX manual shows how broad the application had become. Drawing and page composition lived alongside bitmap placement, symbols, text styles, tracing, color management, and tools for making web graphics and animation.
That breadth could be productive, but it was not automatically elegant. A contemporary CreativePro review of FreeHand MX praised its editable effects and mixed-size pages while also noting that controls could overlap and become confusing.
The appeal was therefore not that every detail was perfect. It was that a useful collection of operations shared a workspace and a set of habits. You could move from adjusting a curve to fitting a photograph into a shape without mentally leaving the job.
The features people are actually remembering
Some features need to be seen in motion to make sense.
Paste Inside made the relationship between a container and its artwork explicit. The clipping shape defined what was visible; the contents remained available for revision. The useful part continued after the initial paste, when the image needed to shift a little without moving the frame.
Multiple pages let related pieces remain visible together. Page size, position, and orientation became part of the working arrangement rather than reasons to split a project into separate documents.
Find & Replace Graphics addressed a different production problem: a design was already full of objects, and something about many of them needed to change. A stroke width, a color, or another property could be treated as a searchable attribute.
Clone and subselection removed smaller interruptions. An exact overlapping copy was different from an offset duplicate. Reaching an object inside a group was different from dismantling the group. Those distinctions seem minor until you repeat the operation throughout a working day.
Typography and the perspective grid extended the same idea: keep the composition editable while its arrangement becomes more sophisticated.
Our feature guide examines twelve of these capabilities without assuming they were all unique inventions.
FreeHand versus Illustrator was never a neutral conversation
In 2009, John Gruber called FreeHand “the greatest app that ever died.” He subsequently included a sharply opposed reaction from an Illustrator user and connected his own preference to his layout-oriented work. His short post captures both the affection and the argument.
A favorite application becomes partly invisible through practice. The hand knows where to go. Another application can offer an equivalent capability while making that hand feel clumsy again.
That is a real cost, but it does not establish that every competing design decision was wrong. Illustrator users had their own expertise, production requirements, and reasons for staying. A fair FreeHand-versus-Illustrator comparison needs to account for both sides, and it needs to separate the products of the early 2000s from the tools available now.
Development had already slowed
The simplest version of this story has Adobe acquiring a thriving product and abruptly turning it off. The contemporary record is more complicated.
When John Nack announced the end of updates in 2007, he noted that MX had arrived nearly four years earlier. In the accompanying discussion, he described an application that had already been largely dormant before Adobe took ownership. That was Adobe’s perspective on the situation, and it belongs in the record alongside users’ objections.
There was also mixed messaging. In May 2006, an Adobe representative told Macworld that support and development would continue according to customer needs. The same statement said development efforts would concentrate on Illustrator and Dreamweaver. Both halves matter. Macworld’s report preserves them.
For someone deciding whether to replace a computer, train a colleague, or migrate an archive, ambiguity was expensive. Even without a new version, a familiar application could remain useful for years. Without updates for future hardware and operating systems, however, that usefulness had a shrinking foundation.
The users tried to change the outcome
Some moved to other programs. Others organized.
Free FreeHand’s effort eventually included an antitrust lawsuit. In February 2012, Judge Lucy Koh allowed most claims to survive Adobe’s motion to dismiss, while granting leave to amend one claim. That was a procedural decision, not a verdict establishing liability. The order makes the distinction important.
Contemporary reporting later described a resolution of the litigation without release of FreeHand’s source code. The campaign article follows the effort and its aftermath, including the search for a successor.
The afterlife includes the files
Nostalgia becomes a practical problem when an old client returns.
A logo in a discontinued file format is still somebody’s logo. A brochure that can only be opened on an aging machine is still part of a business archive. The ability to see a preview is not the same as recovering editable text, intact clipping relationships, or reliable color information.
That is why this series includes both running FreeHand MX and opening and converting old files. They are related questions with different answers. You may need an old installation temporarily to preserve work, while using a modern application for every new job.
The alternatives guide starts with the task you need to recover. The migration guide then translates operations instead of asking you to relearn your profession.
What would happen if we rebuilt the experience?
That question has become a project here at BonFX. It is called Backhand.
Backhand is an independent, browser-first vector editor informed by FreeHand’s documented behavior. The project already contains implementation work for drawing and editing paths, clipping, pages, text, SVG persistence, and bitmap tracing. It also contains the less glamorous material that makes a revival credible: a reference library, behavior specifications, test cases, and explicit gaps.
Those are development facts, not a declaration that FreeHand has been completely replaced. Importing legacy documents, preserving typography and output, and making every operation accessible and dependable remain substantial responsibilities.
We describe the current project separately from what a revival must deliver. You should be able to judge the work without confusing a promising implementation with a finished product.
The FreeHand story deserves more than an obituary. It offers a set of design decisions worth examining, some workflows worth recovering, and a difficult question for anyone building a successor: can a designer trust it with the next job?
Follow Backhand’s development for project notes, demonstrations, and news about testing opportunities when they are ready.
