This year on August 3, Pandoc turned twenty.

For most software projects, that would simply be an anniversary. For Pandoc, it is something more remarkable. In twenty years, operating systems have changed, programming languages have risen and fallen, office suites have come and gone, markup languages have multiplied, and artificial intelligence has begun reshaping how many of us write. Yet through all these changes, Pandoc has quietly continued doing one thing exceptionally well:

It transforms documents.

That may sound ordinary until you stop to think about it.

A Tool That Solved the Real Problem

When people discuss document formats, they often focus on which format is best.

Should we write in Markdown? Should we publish HTML? Should we archive PDF? Should technical manuals use AsciiDoc? Should books use LaTeX? Should reports be written in Word?

John MacFarlane approached the problem from a different direction.

Instead of asking which format should win, he asked a far more practical question:

How do we move information between formats without losing meaning?

That question gave birth to Pandoc.

It is telling that Pandoc is not another document format competing for attention. It is not trying to replace Markdown, HTML, LaTeX, DOCX, EPUB, ODT, or dozens of other formats.

Instead, it became the bridge between them.

In many ways, Pandoc is less about documents than about communication.

Thinking in Transformations

Regular readers of this blog will recognise a familiar theme.

Unix encourages us to think in transformations.

grep transforms files into matching lines.

sed transforms one stream of text into another.

awk transforms records into reports.

sort transforms disorder into order.

uniq transforms repetition into summaries.

Pandoc simply applies this same philosophy to documents.

Instead of viewing a document as something fixed, Pandoc treats it as information that can be represented in many different ways.

A Markdown file becomes HTML.

An HTML document becomes EPUB.

A Word document becomes Markdown.

A LaTeX manuscript becomes PDF.

The source changes.

The ideas remain.

That is perhaps the most Unix-like aspect of Pandoc. It cares less about appearance than about preserving meaning while changing representation.

The Invisible Tool

One of the greatest compliments any Unix utility can receive is that you forget it is there.

Nobody spends much time admiring cat.

Few people celebrate sort.

Most users simply expect grep to work.

Pandoc belongs to this class of software.

Once it becomes part of your workflow, you stop thinking about conversion altogether.

Write once.

Publish anywhere.

That is an extraordinary capability that many modern applications still struggle to match.

Why Open Formats Matter

Proprietary document formats have always enjoyed one significant advantage.

They positioned themselves as the place where information lived.

If everyone exchanged documents in your format, your software became indispensable.

Open formats challenged that assumption.

Markdown demonstrated that documents could be simple.

HTML showed they could be universal.

LaTeX proved they could produce professional typography.

Pandoc connected all of them.

Rather than encouraging lock-in, it encouraged movement.

Your information no longer belonged to a particular application.

It belonged to you.

As textsmiths, this distinction matters enormously.

Our goal is not loyalty to a particular editor or office suite.

Our goal is preserving and communicating ideas.

Pandoc reminds us that documents should travel freely.

Twenty Years in a Changing World

Reading John MacFarlane’s reflections on twenty years of Pandoc is fascinating. The project began as a Haskell program solving a practical need, yet over two decades it has grown into the standard document converter for writers, researchers, publishers, and developers alike. “Twenty Years of Pandoc”

Near the end of his reflections, MacFarlane considers the rise of large language models.

Perhaps one day, he suggests, AI systems will become so capable at converting documents that tools like Pandoc are no longer necessary.

That is an interesting possibility.

But I do not think that day has arrived.

A View from Zimbabwe

Living in Zimbabwe changes how one thinks about software.

Electricity is not something I take for granted.

Neither is an Internet connection.

Cloud-based AI assumes both.

Pandoc assumes neither.

It runs happily on a laptop without network access.

It works on old hardware.

It fits naturally into shell scripts.

It integrates with Git.

It becomes another stage in a pipeline.

That matters.

Around the world there are researchers, students, system administrators, journalists, and programmers who work in environments where reliable connectivity cannot be assumed. For them, an offline tool is not merely a convenience—it is the workflow itself.

This has always been one of Unix’s greatest strengths.

Your tools belong to you.

They continue working whether the network is available or not.

AI Does Not Replace Good Tools

Artificial intelligence will undoubtedly change how we write.

It already has.

But that does not automatically make mature command-line tools obsolete.

History teaches us something different.

Compilers survived IDEs.

Shell scripting survived graphical administration.

Git survived cloud-hosted development platforms.

grep survived desktop search.

Each remained valuable because it solved a specific problem well.

Pandoc belongs in that company.

Even if an AI assistant can eventually convert documents, there will still be immense value in a deterministic, scriptable, offline utility that produces reproducible results every time.

There is room for both.

In fact, AI and Pandoc complement one another remarkably well.

One helps generate ideas.

The other ensures those ideas can travel anywhere.

Happy Birthday, Pandoc

Twenty years is an extraordinary achievement for any open-source project.

Pandoc has never tried to become an office suite.

It has never tried to become another markup language.

It simply became the best translator in the room.

For those of us who think in pipes, filters, and transformations, that is exactly what makes it beautiful.

Happy twentieth birthday, Pandoc.

May your pipelines remain long, your conversions faithful, and your place in the Unix toolbox secure for many years to come.