View Modes
BuildVu has three view modes: idrviewer (the default), content and singlefile (since 2025.10). The mode decides whether your converted document comes with a viewer, or whether displaying it is left to you.
idrviewer (default) | content | singlefile | |
|---|---|---|---|
| What BuildVu writes | An index.html with the IDRViewer built in, plus a file per page | A file per page and no viewer | One self-contained HTML file holding every page (BuildVu-HTML only) |
| Who displays the pages | The IDRViewer, which loads pages on demand | Your own page or application | The browser, which loads every page at once |
| Navigation, zoom and search | Provided by the IDRViewer and the chosen viewer UI | Yours to build | None provided |
| SEO | Not designed for it | Each page can have its own URL and be indexed individually | The whole document is indexed as one page |
| Analytics | A standard tag sees one page load per document opened, so page and search tracking comes from IDRViewer events | A page view per URL your site loads, as with any other page | One page load per document opened |
idrviewer mode:
Choose idrviewer when you want a working viewer without building one. The IDRViewer handles page loading, layouts, zoom and selection, and the provided UIs add navigation, thumbnails and (in the Complete UI) search across the whole document. You can change the default UI or modify the viewer rather than starting from scratch.
The trade-off is that the document lives inside the viewer. Pages load only as the reader approaches them, which keeps large documents fast but means crawlers see only the first pages, and the address bar changes without the page reloading, which is why analytics needs IDRViewer-specific setup.
content mode:
Choose content when the converted pages should become part of your own site or application, with its own navigation, styling, consent handling and analytics. Typical reasons are:
- Giving each page of the document its own URL, so that search engines index each page individually and your analytics tool records a page view for each one without extra code.
- Embedding pages in your own layout or in iframes (see Complete Document).
Everything the IDRViewer would have done becomes yours to build, including navigation, zoom, search and displaying annotations and hyperlinks. That is usually the deciding cost, so choose content mode for how the pages fit into your site, not to save effort.
Some details differ from the viewer output:
- Document metadata is written to
properties.jsoninstead ofconfig.js(Metadata JSON API). - You need to set the character set on the page that displays the content.
- Complete Document, CSS Suffix and Override Page Number are only available in this mode.
singlefile mode:
Choose singlefile when you need the whole document in one HTML file, for example to index it as a single page or for workflows where the output is not loaded in a browser. Every page and asset is embedded, so large or complex documents can be slow to load and may crash the browser, especially on mobile. Use it for small documents only.
Adding analytics:
- idrviewer: add your analytics tag to
index.htmland track the IDRViewer’s events. See the IDRViewer analytics guides. - content: add your tag to the page that displays the converted content, as on any other page of your site. If each document page has its own URL, each one is recorded as a page view. If you show several pages at one URL, or change the page without changing the URL, send your own event each time the page changes.
- singlefile: a tag added to the file records one page load per document opened and nothing else. Measuring how far readers get needs your own scroll tracking. The file is written again by each conversion, so the tag has to be added again after reconverting.