AVATeR e-Reader compatibility

wold March 02, 2022 #AVATeR

Platforms and devices tested with AVATeR are listed below; their limitations are also noted.
For system requirements (for running AVATeR), see the requirements.


AVATeR was originally developed for use with PocketBook readers, and is thus very compatible. Generally, any 6.x and most 5.x firmwares should work with AVATeR.

Tested device/firmware

Translation note support missing

Around firmware 6.7, a new type of note was added that is aimed at learning languages: it stores additional context or dictionary information.


Kobo support was added in v0.14, and is considered experimental, especially for kepub. Firmwares in the 4.x range, upto at least 4.33 are compatible. Later versions are expected to remain compatible.

Tested device/firmware

Any older e-readers/firmware may currently not be supported (drop us a note if you want to help).

No page numbers

For Kobo, page numbers are substituted with the book progress percentage. Page numbers are not (readily) available in the database; retrieving them is possible but complex. Alternatively, use the chapter information (the viewer has an extra column).

Kepub support experimental (v0.14+)

Current Kepub support should work, but may break.


Sony support was added since v0.14, and has some limitations. As Sony has ceased development, support will be stable and improve eventually.

Sony support comes with a fair number of gotchas. Preferably use a memory card to store your books (and thus annotations), and enable the local mirror for the card device.

Tested device/firmware

Annotations limited to 200 characters

Annotations in the DB are limited to 200 characters: a (...) is shown whereever this limit is assumed. Retrieving the full text requires access to the book files, which is still far off. Typed notes are not limited to 200 characters.

Windows: rescan after confirming connection on the device screen

On Windows, when connecting a Sony reader while AVATeR is running, performing a manual re-scan is required (top-left button mainwindow) after you confirmed the connection on the device's screen. For Linux this is fixable with the device monitor, for Windows less so, unless using timers.

Manually select main/card database

Databases on either the main or card storage needs to be manually selected using the (new) source button. The intent is to remember this setting - for now you can however enable the Local Mirror for one storage device (main or card), and avoid manual switching (read on).

Local Mirror limited to one storage

the Local (Database) Mirror feature supports just one storage device at a time: either main or card memory. The LM sync assumes non-overlapping database paths (PocketBook), which the Sony doesn't have. A simple but hacky workaround was explored (using a card subdir), which could work, but was dropped.

Sony SD card always detected

Sony readers always report their SD-card hardware device, and is thus detected by AVATeR, regardless if a card is inserted (and/or mounted). If no card is inserted, some tools (manual backup) may warn about the card storage not being mounted - you may ignore this.

Drawn notes in highlight column

Drawn notes are shown under the Highlight column (not Notes), and omit the highlighed text. This a todo.

Improving XML conversion (todo)

Sony rolled their own (XML) note container format, requiring conversion - future version will improve on the current crude(!) regex using XSTL (on the to-do list).


Vivlio readers use re-branded PocketBook firmware (and possibly hardware), and will generally work with AVATeR.

Tested devices/firmware