MarginaGet Margina
Articles

Published

Why Some Ebook Footnotes Pop Up, and Others Send You to the Back of the Book

A footnote in one ebook app floats over the page and lets you keep reading. The same file, opened somewhere else, drops you at the back of the book with no way back. The difference isn't the book — it's markup most readers never see, built for a reason that has nothing to do with popups.

What it is

Open the same ebook in two different apps and tap the same footnote marker. In one, a small window floats over the page with the note text, and you're back reading a second later. In the other, the screen jumps to the back of the book. Now you're hunting for where you were.

The book didn't change. What changed is how each app handles a small, specific piece of markup called a noteref — a reference to a note, usually the superscript number you tap. The noteref is just the anchor. It doesn't say "pop this up" or "send the reader to the back." It marks that this bit of text points to a note somewhere else in the file, tagged with a separate footnote or endnotes label. What happens when you tap it is entirely up to the app you're reading in.

Why it matters

The file doesn't pick the behavior — the app does

This isn't a guess. In a widely cited publishing forum thread, one practitioner working through an InDesign-to-EPUB export explained it plainly: whether you choose "End of Section" or "Pop-Up" when exporting, the note ends up in the same place in the file — physically at the end of the document or section. The only real difference is whether the app teleports you there with a link, or overlays the text without moving you at all. Both read the exact same markup. The export setting is a hint; the app decides what to do with it.

Built for something other than popups

The markup exists for a more specific reason than convenience. EPUB's accessibility guidelines explain that footnotes and endnotes are content a reader might want to skip and come back to later — especially during audio playback, where a note interrupting mid-sentence is disruptive in a way it isn't on a printed page. Without the footnote and endnotes semantics marking a passage as a note, a reading system can't tell it apart from ordinary body text. It can't offer to skip it, and it can't offer to show it in place either. The popup you see in a good reading app is a side effect of markup built to solve a different problem — the same way EPUB accessibility more broadly depends on a file carrying structure a machine can act on, not just words a person can read.

Where you'll see it

The same file, three different apps, three different experiences

In practice, this plays out inconsistently. Standard EPUB readers tend to show footnotes as a plain block at the end of the document. Apple's Books app hides that block more cleanly, so it reads as a "real" footnote. Kindle files are, by most accounts, the most temperamental of the three — especially once a book mixes footnotes and endnotes, which is common in anything translated from a print edition with both a translator's notes and the author's own citations.

When there's no way back at all

The frustrating case — tap a number, land at the back of the book, find no link back — usually means the note reference was never marked up as a note at all. It's just an ordinary link styled to look like a footnote marker, so the app has no signal that this is a note rather than any other cross-reference. Nothing to offer but the jump. This is the same tension print solved with a fixed rule: a footnote at the bottom of the page costs a glance; one gathered at the back costs a bookmark. Ebooks don't have a fixed "bottom of the page" — what a "page" even means shifts constantly — so that old rule gets rebuilt in software, one app at a time, unevenly.

How Margina handles it

When a file carries proper note markup, Margina shows it as an inline popup. Tap the reference, read the note, tap away — you're exactly where you left off.

What Margina can't do is invent structure that isn't there. If a file's note references were built as plain links rather than proper noteref markup — more common in older or hastily converted files than you'd expect — there's no reliable way to tell a note apart from any other cross-reference, so it opens like any other link. The fix, when there is one, lives in how the file was made, not in how it's read.

Footnotes are, in their own small way, a kind of marginal note built by the author rather than the reader — reaching past the main text to say one more thing without derailing it. A well-marked-up ebook just gives that gesture somewhere sensible to land.

Frequently Asked Questions

Why does the same ebook show popup footnotes on one app and jump to the back of the book on another?

Because the EPUB file only marks a passage as a note reference — it doesn't dictate how that note gets displayed. Whether an app renders it as an overlay or sends you to the backmatter is a decision each reading app makes on its own.

Is there a difference between a footnote and an endnote in an EPUB file?

In current EPUB markup, footnote is the standard term for a note tied to a body passage; endnote is technically deprecated in favor of an endnotes collection semantic, though older files still use it. Either way, the file usually stores the actual note text at the end of the section or document — the popup-vs-jump behavior doesn't depend on which term was used.

Why do some ebooks send you to the back of the book with no way to jump back?

That usually means the note reference wasn't marked up with EPUB's noteref/footnote semantics at all — it's just a plain link. Without that semantic markup, a reading app has no way to know it's looking at a note rather than any other internal link, so it can't offer a popup or a return path.

Does Margina show footnotes as popups?

Margina renders EPUB note references inline as popups where the file includes proper noteref/footnote markup, so you can check a note without losing your place.

Conclusion

The popup-vs-jump split isn't a quirk of any one book. It's what happens when markup built to make notes skippable for accessibility gets reused, app by app, to decide how a note should look. The underlying rule — print's near-note/far-note logic — never really went away. It just lost its fixed home on the page, and every reading app has been rebuilding it a little differently ever since.