EPUB 3.3 itself defines the container, the package document, the content documents and the media overlays. Five further specifications build on it, each for one kind of publication or one extra feature. None changes how a plain book is read; each adds files, attributes or metadata that a reading system that knows it can use. The explorer reads all five (the Companion specs tab of the EPUB viewer) and checks what each says a file must contain.
Multiple-Rendition Publications 1.1
One work, several renditions of it: a reflowable and a fixed-layout version, an English and a French one, a
text version and an audio one. The container already allows several rootfile elements, each naming a
package document; this specification says how a reading system chooses between them. It is a W3C Group Note, last
published 20 January 2026 (epub-multi-rend-11).
Rendition selection attributes
Attributes in the namespace http://www.idpf.org/2013/rendition (conventionally the prefix
rendition) go on the rootfile elements of META-INF/container.xml:
| Attribute | Value | True when |
|---|---|---|
rendition:layout | reflowable or pre-paginated | the reader’s layout preference, when there is one, matches the value |
rendition:media | a CSS 3 media query; a media type in it may only be all | the reading system’s screen satisfies the query, for example (min-width: 1920px) |
rendition:language | a language tag | the reader’s language preference, when there is one, matches the value (the specification relates it to the rendition’s dc:language) |
rendition:accessMode | one or more of auditory, tactile, textual, visual | the reader’s preferred primary access mode matches; it names the rendition’s primary mode, not every mode it contains |
rendition:label | text | never selects; a human-readable name to show in a menu |
The first rootfile is the default rendition. It may carry selection attributes
but need not; every later one must carry at least one selection attribute besides the label. A reading system
evaluates the rootfile elements from the last to the first: it selects the first one
whose rendition attributes are all true, skips one that has none, ignores attributes it does not know, and
reaches the default rendition last. It should do this when the book is opened and again when the environment
changes (the device is turned, the window resized).
Publication metadata: META-INF/metadata.xml
The root is metadata in the namespace http://www.idpf.org/2013/metadata, with the
content model of the package document’s metadata and these differences: a
dc:identifier holds the publication’s unique identifier; exactly one meta with
property="dcterms:modified" and no refines holds the last modified date; the obsolete OPF 2
meta name content form is not allowed; the attributes of package (including
unique-identifier) are allowed on the root; everything else is optional. No metadata is inherited by the
renditions: a reading system needs the default rendition’s own metadata. The unique identifier of the
default rendition is the key for every obfuscated font in the container.
The rendition mapping document
A link in the container’s links element with rel="mapping" names an XHTML
document that tells the reader where the same place in the work is in each rendition, so a reader who switches
rendition lands in the right spot. Its rules:
- no attributes on
html,headorbody(namespace declarations excepted); - the
headholds onlymetaelements, and one of them is<meta name="epub.multiple.renditions.version" content="1.0"/>; - the
bodyholds onlynavelements, exactly one withepub:type="resource-map", and eachnavhas anepub:type; - a resource map is a list of lists: each inner
ulis one place in the work, and its links point to that place in each rendition (one link per rendition). How fine the mapping is, a chapter or a sentence, is up to the publisher.
<rootfile full-path="phone/book.opf" media-type="application/oebps-package+xml"
rendition:label="Phone" rendition:layout="reflowable"/>
<rootfile full-path="tablet/book.opf" media-type="application/oebps-package+xml"
rendition:label="Print replica" rendition:layout="pre-paginated"
rendition:media="(min-width: 1000px)"/>
Reading systems that do not know this specification (and EPUB 2 ones) simply open the default rendition, so it has to be the one every reader can use.
EPUB Indexes 1.0
An index is a navigation aid that lists terms with locators into the book. The specification (idpf.org/epub/idx, an IDPF Recommended Specification) defines how to mark one up so a reading system can use it as an index and not as plain text, and how to ship an index as a publication of its own.
- Markup. The index is an XHTML content document whose
body(or asection) hasepub:type="index". Inside it the structural semantics vocabulary gives each part its meaning:index-group(a letter heading and its entries),index-entry-list,index-entry,index-term,index-locator(a link to the place),index-locator-list,index-locator-range,index-xref-preferred(“see”),index-xref-related(“see also”),index-term-category,index-headnotesandindex-legend. The explorer checks everyepub:typevalue against that vocabulary (structural semantics). - An index publication. A package with
dc:typeindexholds nothing but the index of another work. Its package document has acollection role="index", which may containcollection role="index-group"collections that divide a large index into files, each listing its content documents withlinkelements in reading order. - Embedded index. A book can contain its own index as an ordinary content document marked up as above; the
indexvalue ofschema:accessibilityFeaturesays the book has one.
The explorer lists the dc:type and the collection roles of each package document, reports a type with no
matching collection (and the reverse), and checks the epub:type values inside every content document.
EPUB Dictionaries and Glossaries 1.0
Two ways to hold word lists. A glossary is a list of terms inside a book, marked up with
glossary, glossterm and glossdef. A dictionary is a publication of its own
(idpf.org/epub/dict, an IDPF Recommended Specification):
dc:typedictionaryin the package metadata, and acollection role="dictionary"whoselinkelements name the content documents that hold the entries;- the metadata properties
source-languageandtarget-languagesay which languages it translates from and to; - the entries are
articleelements withepub:type="dictentry"(orcondensed-entry) inside a container markeddictionary, built frompart-of-speech,gram-info,def,tranandtran-info(translations),example,phonetic-transcription,etymology,idiom,sense-list/sense-group,phrase-list/phrase-groupandsynonym-group/antonym-group; - a search key map, a manifest item with the media type
application/vnd.epub.search-key-map+xml, lets a reading system look a word up without scanning the entries: its rootsearch-key-mapholdssearch-key-groupelements, each with anhrefto the entry and thematchelements (value, ortitlewithphonogramfor Japanese) that lead to it.
The explorer lists each search key map with its groups, reports a group whose href is not in the container
or the manifest, and warns when a dictionary has no search key map.
EPUB Previews 1.0
A preview is a sample of a book given away to sell it (idpf.org/epub/previews, an IDPF Recommended Specification). There are two forms:
- A preview publication is an EPUB of its own:
dc:typepreviewin its package metadata, a package identifier that must not be the source book’s (and, as the specification advises, not an ISBN), and adc:sourceholding the source book’s identifier, which it should have.link rel="acquire"elements say where the full book can be had. - An embedded preview is part of the full book, named by a
collection role="preview"in its package document. The collection holds acollection role="manifest"listing every content document and resource the preview needs (so a shop can extract it), andlinkelements in reading order naming the content documents shown. Alinkmay end in a fragment identifier, and then it names a range: from the start of the document up to, not including, the element the fragment names, so a preview can end in the middle of a chapter. The reading system must show the previewed content and offer a way to acquire the whole book.
The explorer reports a preview that shares its source’s identifier, a preview with no dc:source, and an empty preview collection.
EPUB Text-to-Speech Enhancements 1.0
A reading system that speaks the text with a synthetic voice can get the pronunciation wrong for names, foreign words, abbreviations and homographs. The specification (epub-tts-10, a W3C Group Note of 28 August 2025) gives authors two ways to say how a word is said:
- PLS pronunciation lexicons. A file of media type
application/pls+xml, a W3C Pronunciation Lexicon Specification 1.0 document: the rootlexicon(namespacehttp://www.w3.org/2005/01/pronunciation-lexicon,version="1.0", anxml:lang, optionally analphabet), whoselexemeelements each have one or moregrapheme(the written form) and aphoneme(the pronunciation) or analias(say this other text instead). A content document links it from itsheadwith<link rel="pronunciation" type="application/pls+xml" hreflang="fr" href="fr.pls"/>, one link for each language; an SVG content document does the same. - SSML attributes on the text. With the namespace
http://www.w3.org/2001/10/synthesis(prefixssml),ssml:phgives the pronunciation of the element’s text as phonemes andssml:alphabetnames the alphabet (ipain the specification’s examples). They apply to the element’s text and override a lexicon.
The explorer reads every lexicon in the manifest (the Companion specs tab lists each lexeme), counts ssml:ph,
ssml:alphabet and the pronunciation links in each content document, and reports a link without the right
type or without hreflang, an empty ssml:ph, an unknown attribute in the SSML namespace and a lexeme with no
pronunciation.
What the explorer checks, in one list
- container.xml: the five
rendition:*attributes (values, the rule that a later rendition needs a selection attribute, unknown attributes in the namespace), the order a reading system tries the renditions, the mapping link and its media type; - metadata.xml: the root, the unique identifier, exactly one
dcterms:modified, no OPF 2meta; the mapping document: itshead,body,navrules and where every link leads (and whether some rendition lists it); - the package:
dc:typeand collection roles for indexes, dictionaries and previews, the preview identifier and source rules, search key maps, PLS lexicons, and the SSML andlink rel="pronunciation"markup in content documents.
Reading systems also have to follow rules the book cannot show: which rendition they pick, how a mapping is used, how a dictionary lookup works. Those belong to the Reading Systems specification and are outside what a file can be checked for.