One File, Many Formats

How InDesign’s Export Structure Makes Smarter Multi-Format Publishing Possible

If you read our post on how paragraph styles control PDF accessibility, you know that every paragraph style in InDesign can carry an Export Tag: a hidden label that helps define what each piece of content is when the document is exported.

But in the EPUB and HTML side of that same Export Tagging panel, there’s another field we didn’t cover. It’s called Class, it’s often left blank, and for designers working only on a single print PDF, it may not matter much.

For designers managing content that needs to live in more than one format, it matters a lot.

This post is for designers and communications professionals who are thinking about content efficiency: building structured source files that can move more cleanly into print PDF, accessible PDF, EPUB and web without rebuilding from scratch every time the format changes.

First, a Quick Analogy

If you've worked with a website platform like Squarespace, you've probably noticed that it offers multiple paragraph styles — sometimes labeled P1, P2, P3, or Body, Body Large, Body Small. These all look different on the page, but they're all semantically the same thing: a paragraph. In HTML terms, they all render as <p> tags. The numbering describes the visual variant, not the reading role.

InDesign works the same way, and the Export Tagging panel is where that distinction lives.

The Tag field defines the semantic role: what the content is. p means paragraph. h2 means second-level heading. li means list item. This is what screen readers and assistive technology pay attention to.

The Class field defines the visual variant: what the content looks like within that role. It's a free-text label you invent and assign, and it travels with the content when you export to EPUB or HTML.

Together, they let you write something like this in your exported code:

<p class="body-lead">This is the introductory paragraph.</p>

<p class="body">This is standard body text.</p>

<p class="caption">This is a caption beneath an image.</p>

Three different paragraph styles in InDesign. Three different visual treatments on the page. One semantic tag — p — that correctly tells every reader, human or machine, that all three are paragraphs.

Why the Tag/Class Separation Is Worth Understanding

This isn't just a technical detail. It reflects a fundamental principle of structured content: meaning and appearance are separate concerns.

The tag answers: What is this? The class answers: How should this look?

When you collapse those two questions into one — when you choose a heading style because it makes text look big and bold, rather than because it marks a structural section — you create a document where meaning and appearance are tangled together. It works fine if you only ever export to one format and no one ever uses a screen reader. It breaks in almost every other situation.

The designers and communicators who think in terms of tags and classes tend to build documents that are more durable, more reusable, and more accessible. Not because they're following rules, but because they've separated the question of what something is from the question of what it looks like — and those two things can be changed independently.

What to Put in the Class Field

Class names are yours to invent. If you leave the field blank, InDesign may generate class names from your style names during EPUB or HTML export, which is another reason to name styles intentionally instead of letting a file accumulate mystery labels over time. InDesign doesn't validate them or enforce any naming convention. A few guidelines that will serve you well:

• Use lowercase with hyphens. body-lead not Body Lead or bodyLead. This matches standard CSS convention and will save you headaches if the class names land in a stylesheet.

• Name for role, not appearance. intro-paragraph is better than large-text because if you ever change the size, the class name still makes sense. pull-quote is better than blue-box for the same reason.

• Be consistent across documents. If you use caption in one document and fig-caption in another, your EPUB stylesheets will need separate rules for each. Pick a convention and stick to it.

Here's a starter set that works for most communications documents:

InDesign Style Name	Export Tag	Export Class
Body Text	p	body
Body — Lead Paragraph	p	body-lead
Caption	p	caption
Pull Quote	p	pull-quote
Callout Text	p	callout
Sidebar Text	p	sidebar
Section Intro	p	section-intro
Fine Print	p	fine-print

All of these export as <p> tags — semantically identical, visually distinct, and individually styleable.

Where Classes Actually Work: EPUB and HTML Export

Here's the honest part, because this distinction matters for deciding whether to bother with the Class field at all.

• In accessible PDF export: the tag is what matters. PDF tag structure does not use CSS classes the way HTML does, and assistive technology is not relying on your InDesign class names to interpret the document. For print PDF accessibility, focus first on headings, paragraphs, lists, tables, artifacts, reading order, and alt text. The Class field will not do the heavy lifting there.

• In EPUB export: this is where the tag/class system earns its keep. InDesign can write class names into the EPUB’s XHTML markup and generate CSS that travels inside the EPUB package. You can edit that CSS, replace it or map it to a cleaner stylesheet after export. If you are producing EPUB versions of annual reports, program guides or publications that need to work across devices, building intentional classes into your InDesign styles can save significant cleanup later.

• In HTML export: same principle. InDesign’s HTML export usually requires cleanup, but tag/class structure gives you a more meaningful starting point than a pile of generic or auto-generated markup.

The practical upshot: If you work exclusively in print PDF, the Class field is optional. If you produce content in multiple formats — or think you might someday — building the class names into your paragraph styles costs almost nothing up front and pays dividends every time you repurpose the file.

The Bigger Workflow: One Source, Many Outputs

The tag/class system is one piece of a larger idea that's worth naming directly: single-source publishing.

The premise is that you build one well-structured source document — in InDesign, or in a content management system, or in a structured authoring tool — and you derive multiple output formats from it. Print PDF for the funder packet. Accessible tagged PDF for the website. EPUB for the digital library. HTML for the email newsletter. Each output looks appropriate for its medium. All of them come from the same source content, with the same meaning intact.

This is how book publishers, academic journals, and large content operations work. It's increasingly how sophisticated communications teams are starting to work, too, especially as audiences expect content to be available in more than one format.

InDesign isn't a perfect single-source publishing tool — it was designed for print, and the EPUB and HTML exports reflect that. But it's capable enough that a document built with good style discipline, proper export tags, and thoughtful class names can be the starting point for multiple output formats without being rebuilt from scratch.

The investment is mostly upfront: deciding on your style names, setting your tags and classes, and building templates that encode those decisions so you don't have to make them every time. After that, the structure travels with every document you produce from those templates.

A Note on Inherited Styles

One more thing worth knowing: InDesign paragraph styles support inheritance. You can create a "parent" style — say, Body Text — and then create child styles that inherit all of its properties and override specific ones. Body Text - Lead might inherit everything from Body Text and simply add a slightly larger size or different color.

This inheritance works in the Export Tagging panel too. If you set the tag and class on the parent style, child styles will inherit those settings unless you override them. This means you can establish your tag/class structure at the parent level and have it flow through your entire style system automatically, which is useful if you're managing a large template with many style variants.

The catch: InDesign doesn't always export inherited styles cleanly, particularly for complex EPUB outputs. Test your export early in the process rather than at the end.

The Bottom Line

The tag/class distinction in InDesign's Export Tagging panel is a small setting with a large implication: it's where the separation between meaning and appearance lives in your document.

For most print designers, the tag alone is what matters. Get your heading hierarchy right, tag your paragraphs and lists correctly, and your accessible PDF will hold up. But for designers and communications teams who are starting to think about content that needs to work in multiple formats, the Class field is where that ambition gets built into the document structure from day one.

Build it in once. Export it everywhere. That's the workflow.