PDF turns 33 this year. And if you work in product data management, it has probably been part of your output chain for most of that time, whether you think about it or not.

That might sound like a strange claim to lead with. We live in a world of interactive web experiences, real-time collaboration tools, and AI-generated content. Surely the humble PDF, a static, fixed-layout document, should have been retired by now?

It hasn't. And when you look at why, it starts to make perfect sense.

The problem PDF was built to solve

In the late 1980s, a team at Adobe led by co-founder John Warnock faced a frustration that anyone working with documents at the time would recognise: you could create a beautiful document on your computer, but the moment you sent it to someone else, on a different machine, a different operating system, a different printer, the formatting fell apart.

Fonts changed. Layouts shifted. Colours looked different. What you saw was not what they got.

Warnock's vision, outlined in what became known as the "Camelot" memo, was simple and ambitious: create a universal way to capture and send documents so they looked exactly the same everywhere, on any device, on any screen, from any printer.

In 1993, Adobe released PDF 1.0. The format solved a universal problem: how to share a document and guarantee that every recipient sees exactly what the author intended. No reflow. No broken layouts. No missing fonts.

That core promise of fidelity and portability has not been replaced by any format since.

Three decades of quiet evolution

What most people miss about PDF is that it has not stood still. While the basic premise remains the same, the format has evolved through a series of ISO standards that reflect changing enterprise needs.

PDF/X (2001) introduced standards for print production, ensuring that PDFs used in commercial printing contained everything needed for reliable reproduction: embedded fonts, correct colour spaces, no ambiguity.

PDF/A (2005) addressed long-term archiving. Regulated industries, government agencies, and compliance-heavy organisations needed a format that could be stored for decades and remain readable without depending on external resources. PDF/A removed features that could break over time (like external font references or JavaScript) and created a self-contained, preservation-ready document.

ISO 32000 (2008) marked the moment PDF became a fully open international standard, no longer controlled solely by Adobe. This was a turning point. It meant the format's evolution was governed by an international standards body, giving enterprises confidence that PDF would remain stable, interoperable, and vendor-neutral.

PDF/UA (2012, updated 2024) tackled accessibility. As digital inclusion became a legal requirement, not just a nice-to-have, PDF/UA defined how documents should be structured so screen readers and assistive technologies could interpret them correctly. With the European Accessibility Act now in effect as of June 2025, this standard has moved from "recommended" to "required" for many organisations.

PAdES signatures (updated 2024) brought legally binding digital signatures into the PDF ecosystem, aligned with the EU's eIDAS regulation. Contracts, agreements, and compliance documents can be digitally signed within a PDF and carry the same legal weight as a wet signature.

Each of these standards responded to a real enterprise need. Together, they transformed PDF from a simple "what you see is what you get" format into a comprehensive enterprise content platform covering print fidelity, long-term archiving, accessibility compliance, and legal authentication.

Why enterprises still depend on PDFs today

Despite the rise of web-first content strategies, PDFs remain deeply embedded in how enterprises actually work. Not because people are slow to change, but because PDFs solve problems that other formats still cannot.

Compliance and archiving. Regulated industries need documents that can be stored, retrieved, and verified years or even decades later. PDF/A remains the standard recommendation for page-oriented documents intended for long-term preservation. No web page offers this guarantee.

Partner and channel distribution. When you send a product datasheet to a distributor, a retailer, or a channel partner, you need it to look right on their screen, print correctly in their office, and survive being forwarded to three more people. PDFs do this. HTML emails and web links do not always travel well through enterprise firewalls, offline environments, and legacy systems.

Sales enablement. Sales teams need portable, self-contained documents they can share in a meeting, attach to an email, or present offline. Case studies, spec sheets, pricing summaries, and proposals are overwhelmingly distributed as PDFs, because they work in every situation, including the ones where Wi-Fi does not.

Legal and contractual workflows. With PAdES digital signatures aligned to eIDAS, PDFs are now the container of choice for signed agreements across Europe. Contracts, declarations of conformity, and audit documents live in PDF because the legal infrastructure is built around it.

Accessibility regulation. The European Accessibility Act, effective since June 2025, requires digital products and services to meet accessibility standards. For organisations distributing customer-facing documents, this means producing accessible, structured PDFs. Not abandoning the format, but governing it properly.

PDF and the STEP platform: a long shared history

If you have worked with STEP from Stibo Systems, you know that PDF has been a core output channel from the platform for years. The STEP Publisher, STEP's integration with Adobe InDesign Server, has long enabled organisations to take governed product data from their STEP platform and flow it directly into professionally designed templates, producing print-ready catalogues, datasheets, and specification documents at scale.

That pipeline (trusted data in, governed PDF out) was ahead of its time. It recognised something that many organisations are only now catching up to: the PDF is not just a document. It is a compiled output from your master data, and it should be treated as such.

The challenge has always been making that capability accessible. InDesign Server is a powerful tool, but it comes with its own complexity, licensing considerations, and skill requirements. Not every team that needs product PDFs has a desktop publishing specialist on hand.

That is exactly the space that has been evolving lately. The question is no longer whether PDF belongs in your product data workflow. It clearly does. The question is how to make PDF generation simpler, faster, and available to the people who actually need it – at scale.

What comes next

Every few years, someone declares PDF dead. And every few years, the enterprise world quietly continues to depend on it, because no alternative solves the same combination of problems.

What is changing, and what should change, is not the format itself, but how PDFs are created. The era of manually assembling PDFs from scratch, copy-pasting product data into templates, and hoping the latest version is the right one should be behind us.

The document that John Warnock imagined in 1989 was meant to look the same everywhere. The enterprise PDF of 2026 should also be accurate, current, accessible, and created in seconds rather than days.

PDF is not old technology. It is proven infrastructure. And the organisations that treat it as such will have a significant advantage in how they communicate, comply, and compete.

If this topic resonates with you, we are co-hosting a webinar with Stibo Systems on 16 April where we will dig into the overlooked PDF automation capabilities of the STEP Publisher and share a first look at what is coming next. It is called "Keep Your PDFs Automatically Updated and in Sync", and you can register here.