The Promise of a Color
For most people, color feels like one of the last free things.
You see it before you name it. The red of a stop sign. The blue of a corporate logo. The soft cream of an old paper stock. The exact orange of a package you can recognize from across a grocery aisle before you can read a single word. Color belongs to memory before it belongs to commerce.
But in professional design, color has never been only a feeling. It is also a system. A number. A swatch. A standard. A promise that what leaves the designer’s screen will arrive, as faithfully as possible, on paper, packaging, fabric, plastic, signage, or the wall of a trade show booth.
That promise is why Pantone mattered.
Pantone’s modern importance comes from the Pantone Matching System, introduced in the 1960s as a standardized color language for designers, printers, manufacturers, and brands. Before systems like this became common, “red” could mean one thing to a designer, another to a printer, and something else entirely once ink hit coated paper, uncoated paper, plastic, fabric, or metal. Pantone gave the industry a way to point to color with precision. A designer could specify a Pantone number, and a printer could understand not only the idea of a color, but the intended production result.
For decades, that system became part of the ordinary infrastructure of design. It lived in physical fan decks, brand guidelines, production files, packaging specs, press checks, environmental graphics, and eventually Adobe applications. Designers working in Illustrator, InDesign, and Photoshop could open a color book, choose a Pantone swatch, assign it to a logo, and send the file into the world with some confidence that the color had a shared reference point.
When the Swatches Disappeared
Then, in 2022, that infrastructure changed.
Adobe announced in July 2022 that some Pantone Color Books preloaded in Illustrator, InDesign, and Photoshop would be phased out from future software updates beginning in August 2022. After November 2022, the only Pantone books Adobe said would remain built into the apps were Pantone + CMYK Coated, Pantone + CMYK Uncoated, and Pantone + Metallic Coated. For the complete set of Pantone libraries, users would need to install Pantone Connect, a separate Adobe plug-in, and purchase a premium Pantone license.
Pantone’s explanation was that the built-in Adobe libraries were outdated. According to Pantone, the Pantone Color libraries inside Creative Cloud had not been updated by Adobe in more than ten years. As a result, the default Adobe applications were missing more than 800 Pantone Matching System colors and nearly 5,000 Fashion, Home + Interiors colors. Pantone and Adobe, Pantone said, agreed to stop distributing those older libraries through Creative Cloud in November 2022 and move users toward Pantone Connect instead.
On paper, it sounded like maintenance: a licensing change, a modernization effort, a cleaner path to updated color libraries.
In practice, it landed like a betrayal.
Designers opened old files and saw missing colors, inaccessible libraries, broken workflows, and, in some cases, colors that rendered gray or black. The technical truth is more specific than the panic: Pantone’s own support guidance said older Photoshop files should render normally in Photoshop versions released in or after November 2022, while Photoshop versions from August, September, and October 2022 could render unavailable Pantone colors gray or black. Illustrator and InDesign behaved differently, with existing swatches generally preserved more reliably than many early social posts suggested.
But the emotional truth was simpler: people opened professional files and no longer trusted what they saw.
The Community Reaction
That is where the story becomes bigger than Pantone.
A missing color is not just a technical inconvenience. It is a broken chain of confidence. Designers do not use Pantone because they enjoy navigating proprietary libraries. They use it because color is one of the most fragile parts of production. A brand color that looks perfect on a calibrated monitor can shift when printed on uncoated stock. A beautiful blue can dull on fabric. A rich red can become muddy in process color. A corporate color can look expensive in one environment and cheap in another.
The Pantone number is a handshake across distance: designer to printer, agency to vendor, headquarters to factory, screen to material world.
When that handshake becomes a separate subscription, the reaction is not only about money. It is about dependency.
Adobe Creative Cloud is already a subscription. For many working designers, it is not optional. Photoshop, Illustrator, and InDesign are the floor of the profession, not luxury add-ons. Pantone, too, is not simply decorative. In print, packaging, apparel, environmental graphics, product design, and brand systems, it has long functioned as part of the professional language.
So the Adobe-Pantone break felt like a double lock: the software is rented, and now part of the color infrastructure inside the software is rented separately.
That was the anger that moved through the design community. On Adobe’s own forums, users complained that Pantone swatch books had disappeared from Illustrator after updates, that backup libraries no longer behaved as expected, and that they were being forced to troubleshoot color systems in the middle of real production work. One frustrated user described coming into the office for rush work only to discover that the libraries were gone. The emotional center of the complaint was not abstract. It was practical: stop messing with my workflow.
On Reddit, the reaction was even more direct. Designers and print workers described the change as a headache, a feud between large companies that left working professionals to clean up the mess. A print shop user explained that customers still expected them to set up files and match specific PMS colors, but after updating Adobe software, the automatic Pantone books were gone. Others complained that Pantone Connect was clunky, unreliable, or simply another fee in a profession already crowded with subscriptions. Some shared workarounds. Some said to use old libraries. Some said to name spot colors manually and coordinate directly with printers. Some shrugged and said experienced production designers should know how to survive without the plug-in.
But underneath the practical advice was a shared irritation: a standard that once felt embedded in the workflow had become conditional.
The File Became Less Stable
That is the real story. Not that a company charged for a tool. Companies charge for tools. Not that Pantone wanted to modernize its libraries. Standards do need maintenance. Not even that Adobe and Pantone failed to make their business agreement invisible to users, though mature infrastructure is supposed to feel invisible.
The deeper story is that the creative file itself became less stable.
A designer could create a file under one set of assumptions and reopen it under another. A brand asset that once contained production-ready color information could become dependent on a license, a plug-in, an account, a plan, an app version, or a corporate agreement between two companies the designer does not control. The file was no longer just a file. It was a doorway into a stack of permissions.
That is the quiet anxiety of subscription infrastructure. It does not always announce itself as loss. It arrives as a missing menu, a disabled feature, a plug-in prompt, a licensing notice, a library that used to be there and now is not. The object you thought you had becomes a service you are temporarily allowed to access.
For designers, this cuts against the grain of craft.
Design is already full of uncertainty: client interpretation, production error, compressed timelines, shifting budgets, late-stage revisions, vendors with different equipment, executives who see color differently under conference room lights. Systems like Pantone existed to reduce that uncertainty. They gave creative work a bridge into manufacturing. They allowed taste to become specification.
That bridge now has a toll booth.
The Price of Access
At the time of the backlash, reports focused on Pantone Connect costing about $15 per month. Pantone’s current listed individual pricing is $29.99 per month or $89.99 per year. For a large agency, that may be a manageable budget line. For a freelancer, student, nonprofit designer, apparel artist, small studio, or independent print shop, it is another recurring fee layered on top of Adobe, fonts, stock, plug-ins, cloud storage, rendering services, project management software, AI tools, and everything else that now arrives as a monthly charge.
The defenders of the move have a point. Pantone is a private company. It maintains color systems, produces guides, updates libraries, builds tools, and sells access. The old Adobe libraries were not fully current. Pantone Connect does provide access to broader and more updated libraries than the aging built-in books.
But the criticism has a point too: infrastructure feels different from software.
Once a standard becomes deeply embedded in an industry, removing it from the default toolchain does not feel like a product update. It feels like a public road being privatized after everyone has built their commute around it.
The Adobe-Pantone split is not really about whether color itself can be owned. Individual colors are not owned in the ordinary human sense. No one owns the blue of a summer sky or the red of a wound or the yellow of a porch light at dusk. But color systems can be controlled. Libraries can be licensed. Names can be protected. Workflows can be gated. Access can be granted, removed, metered, bundled, unbundled, and resold.
That is the modern creative economy in miniature.
The Subscription-Era Design Stack
The designer’s world used to be built around objects: a Mac, a software box, a printed swatch book, a hard drive full of files, a shelf of references, a binder of brand standards. Now it is built around access: cloud apps, synced fonts, licensed stock, plug-ins, AI credits, seats, tokens, enterprise permissions, and services stacked on top of services. The work may still feel personal, but the tools increasingly behave like leased utilities.
Pantone leaving Adobe exposed how much of creative practice now rests on agreements designers never see.
A contract changes somewhere between two companies, and suddenly a production workflow changes inside a designer’s file. A licensing model shifts, and a color that once appeared as part of the design environment becomes an external service. The designer is left to explain it to the client, patch the file, pay the fee, find a workaround, call the printer, or rebuild the system.
That is why the reaction was emotional.
Because color is not just data. It is memory. It is brand equity. It is recognition. It is the thing a customer sees before language. It is the red on the box, the blue on the sign, the green on the label, the yellow that makes something feel warm instead of cheap. Designers spend years training their eyes to see small differences most people feel but cannot name. Pantone gave those differences names.
And then, for many users, those names moved behind a login.
The Real Question
This is where the story becomes less about Pantone and Adobe, and more about the future of creative ownership.
What happens when the basic ingredients of making are no longer stable parts of the tool, but services layered on top of services? What happens when the archive depends on active subscriptions? What happens when the file is no longer a finished artifact, but a live negotiation between software, licensing, and corporate agreements?
The Adobe-Pantone split did not end professional color management. Designers still use physical Pantone guides. Printers still understand PMS callouts. Spot colors can still be created manually. Many Illustrator and InDesign files continued to behave normally. Not every workflow broke. Not every designer needed Pantone Connect. The panic was not universal, and some of the early online anger flattened important technical distinctions.
But the symbolism stuck.
Because the question was never only, “How do I get my swatches back?”
The question was, “How much of my work do I actually control?”
In that sense, Pantone did not simply leave Adobe. It revealed Adobe, Pantone, and the whole subscription-era design stack for what it has become: a beautiful machine made of dependencies.
And somewhere inside that machine is a designer opening an old file, looking for a color that used to be there, and discovering that even memory now has a renewal date.
The Promise of a Color
For most people, color feels like one of the last free things.
You see it before you name it. The red of a stop sign. The blue of a corporate logo. The soft cream of an old paper stock. The exact orange of a package you can recognize from across a grocery aisle before you can read a single word. Color belongs to memory before it belongs to commerce.
But in professional design, color has never been only a feeling. It is also a system. A number. A swatch. A standard. A promise that what leaves the designer’s screen will arrive, as faithfully as possible, on paper, packaging, fabric, plastic, signage, or the wall of a trade show booth.
That promise is why Pantone mattered.
Pantone’s modern importance comes from the Pantone Matching System, introduced in the 1960s as a standardized color language for designers, printers, manufacturers, and brands. Before systems like this became common, “red” could mean one thing to a designer, another to a printer, and something else entirely once ink hit coated paper, uncoated paper, plastic, fabric, or metal. Pantone gave the industry a way to point to color with precision. A designer could specify a Pantone number, and a printer could understand not only the idea of a color, but the intended production result.
For decades, that system became part of the ordinary infrastructure of design. It lived in physical fan decks, brand guidelines, production files, packaging specs, press checks, environmental graphics, and eventually Adobe applications. Designers working in Illustrator, InDesign, and Photoshop could open a color book, choose a Pantone swatch, assign it to a logo, and send the file into the world with some confidence that the color had a shared reference point.
When the Swatches Disappeared
Then, in 2022, that infrastructure changed.
Adobe announced in July 2022 that some Pantone Color Books preloaded in Illustrator, InDesign, and Photoshop would be phased out from future software updates beginning in August 2022. After November 2022, the only Pantone books Adobe said would remain built into the apps were Pantone + CMYK Coated, Pantone + CMYK Uncoated, and Pantone + Metallic Coated. For the complete set of Pantone libraries, users would need to install Pantone Connect, a separate Adobe plug-in, and purchase a premium Pantone license.
Pantone’s explanation was that the built-in Adobe libraries were outdated. According to Pantone, the Pantone Color libraries inside Creative Cloud had not been updated by Adobe in more than ten years. As a result, the default Adobe applications were missing more than 800 Pantone Matching System colors and nearly 5,000 Fashion, Home + Interiors colors. Pantone and Adobe, Pantone said, agreed to stop distributing those older libraries through Creative Cloud in November 2022 and move users toward Pantone Connect instead.
On paper, it sounded like maintenance: a licensing change, a modernization effort, a cleaner path to updated color libraries.
In practice, it landed like a betrayal.
Designers opened old files and saw missing colors, inaccessible libraries, broken workflows, and, in some cases, colors that rendered gray or black. The technical truth is more specific than the panic: Pantone’s own support guidance said older Photoshop files should render normally in Photoshop versions released in or after November 2022, while Photoshop versions from August, September, and October 2022 could render unavailable Pantone colors gray or black. Illustrator and InDesign behaved differently, with existing swatches generally preserved more reliably than many early social posts suggested.
But the emotional truth was simpler: people opened professional files and no longer trusted what they saw.
The Community Reaction
That is where the story becomes bigger than Pantone.
A missing color is not just a technical inconvenience. It is a broken chain of confidence. Designers do not use Pantone because they enjoy navigating proprietary libraries. They use it because color is one of the most fragile parts of production. A brand color that looks perfect on a calibrated monitor can shift when printed on uncoated stock. A beautiful blue can dull on fabric. A rich red can become muddy in process color. A corporate color can look expensive in one environment and cheap in another.
The Pantone number is a handshake across distance: designer to printer, agency to vendor, headquarters to factory, screen to material world.
When that handshake becomes a separate subscription, the reaction is not only about money. It is about dependency.
Adobe Creative Cloud is already a subscription. For many working designers, it is not optional. Photoshop, Illustrator, and InDesign are the floor of the profession, not luxury add-ons. Pantone, too, is not simply decorative. In print, packaging, apparel, environmental graphics, product design, and brand systems, it has long functioned as part of the professional language.
So the Adobe-Pantone break felt like a double lock: the software is rented, and now part of the color infrastructure inside the software is rented separately.
That was the anger that moved through the design community. On Adobe’s own forums, users complained that Pantone swatch books had disappeared from Illustrator after updates, that backup libraries no longer behaved as expected, and that they were being forced to troubleshoot color systems in the middle of real production work. One frustrated user described coming into the office for rush work only to discover that the libraries were gone. The emotional center of the complaint was not abstract. It was practical: stop messing with my workflow.
On Reddit, the reaction was even more direct. Designers and print workers described the change as a headache, a feud between large companies that left working professionals to clean up the mess. A print shop user explained that customers still expected them to set up files and match specific PMS colors, but after updating Adobe software, the automatic Pantone books were gone. Others complained that Pantone Connect was clunky, unreliable, or simply another fee in a profession already crowded with subscriptions. Some shared workarounds. Some said to use old libraries. Some said to name spot colors manually and coordinate directly with printers. Some shrugged and said experienced production designers should know how to survive without the plug-in.
But underneath the practical advice was a shared irritation: a standard that once felt embedded in the workflow had become conditional.
The File Became Less Stable
That is the real story. Not that a company charged for a tool. Companies charge for tools. Not that Pantone wanted to modernize its libraries. Standards do need maintenance. Not even that Adobe and Pantone failed to make their business agreement invisible to users, though mature infrastructure is supposed to feel invisible.
The deeper story is that the creative file itself became less stable.
A designer could create a file under one set of assumptions and reopen it under another. A brand asset that once contained production-ready color information could become dependent on a license, a plug-in, an account, a plan, an app version, or a corporate agreement between two companies the designer does not control. The file was no longer just a file. It was a doorway into a stack of permissions.
That is the quiet anxiety of subscription infrastructure. It does not always announce itself as loss. It arrives as a missing menu, a disabled feature, a plug-in prompt, a licensing notice, a library that used to be there and now is not. The object you thought you had becomes a service you are temporarily allowed to access.
For designers, this cuts against the grain of craft.
Design is already full of uncertainty: client interpretation, production error, compressed timelines, shifting budgets, late-stage revisions, vendors with different equipment, executives who see color differently under conference room lights. Systems like Pantone existed to reduce that uncertainty. They gave creative work a bridge into manufacturing. They allowed taste to become specification.
That bridge now has a toll booth.
The Price of Access
At the time of the backlash, reports focused on Pantone Connect costing about $15 per month. Pantone’s current listed individual pricing is $29.99 per month or $89.99 per year. For a large agency, that may be a manageable budget line. For a freelancer, student, nonprofit designer, apparel artist, small studio, or independent print shop, it is another recurring fee layered on top of Adobe, fonts, stock, plug-ins, cloud storage, rendering services, project management software, AI tools, and everything else that now arrives as a monthly charge.
The defenders of the move have a point. Pantone is a private company. It maintains color systems, produces guides, updates libraries, builds tools, and sells access. The old Adobe libraries were not fully current. Pantone Connect does provide access to broader and more updated libraries than the aging built-in books.
But the criticism has a point too: infrastructure feels different from software.
Once a standard becomes deeply embedded in an industry, removing it from the default toolchain does not feel like a product update. It feels like a public road being privatized after everyone has built their commute around it.
The Adobe-Pantone split is not really about whether color itself can be owned. Individual colors are not owned in the ordinary human sense. No one owns the blue of a summer sky or the red of a wound or the yellow of a porch light at dusk. But color systems can be controlled. Libraries can be licensed. Names can be protected. Workflows can be gated. Access can be granted, removed, metered, bundled, unbundled, and resold.
That is the modern creative economy in miniature.
The Subscription-Era Design Stack
The designer’s world used to be built around objects: a Mac, a software box, a printed swatch book, a hard drive full of files, a shelf of references, a binder of brand standards. Now it is built around access: cloud apps, synced fonts, licensed stock, plug-ins, AI credits, seats, tokens, enterprise permissions, and services stacked on top of services. The work may still feel personal, but the tools increasingly behave like leased utilities.
Pantone leaving Adobe exposed how much of creative practice now rests on agreements designers never see.
A contract changes somewhere between two companies, and suddenly a production workflow changes inside a designer’s file. A licensing model shifts, and a color that once appeared as part of the design environment becomes an external service. The designer is left to explain it to the client, patch the file, pay the fee, find a workaround, call the printer, or rebuild the system.
That is why the reaction was emotional.
Because color is not just data. It is memory. It is brand equity. It is recognition. It is the thing a customer sees before language. It is the red on the box, the blue on the sign, the green on the label, the yellow that makes something feel warm instead of cheap. Designers spend years training their eyes to see small differences most people feel but cannot name. Pantone gave those differences names.
And then, for many users, those names moved behind a login.
The Real Question
This is where the story becomes less about Pantone and Adobe, and more about the future of creative ownership.
What happens when the basic ingredients of making are no longer stable parts of the tool, but services layered on top of services? What happens when the archive depends on active subscriptions? What happens when the file is no longer a finished artifact, but a live negotiation between software, licensing, and corporate agreements?
The Adobe-Pantone split did not end professional color management. Designers still use physical Pantone guides. Printers still understand PMS callouts. Spot colors can still be created manually. Many Illustrator and InDesign files continued to behave normally. Not every workflow broke. Not every designer needed Pantone Connect. The panic was not universal, and some of the early online anger flattened important technical distinctions.
But the symbolism stuck.
Because the question was never only, “How do I get my swatches back?”
The question was, “How much of my work do I actually control?”
In that sense, Pantone did not simply leave Adobe. It revealed Adobe, Pantone, and the whole subscription-era design stack for what it has become: a beautiful machine made of dependencies.
And somewhere inside that machine is a designer opening an old file, looking for a color that used to be there, and discovering that even memory now has a renewal date.
(COMMENTARY)
