docs/frequently-asked-questions.md
You can open an issue here for bug reports, feature requests, or specialized help. For bug reports, attach your log file (see Where Can I Find the Log File? below). Reports with limited information or no log may get limited or delayed help.
Libation keeps its log files in your Libation files folder. When reporting a bug, attach the Libation log file from that folder. If the folder contains LibationCrash.log, attach that too.
Default log folder locations
| Platform | Folder |
|---|---|
| Windows | %userprofile%\Libation |
| macOS | ~/Library/Application Support/Libation |
| Linux | ~/.local/share/Libation |
macOS: If that folder does not exist because Libation never starts, try launching from Terminal and note whether it works: /Applications/Libation.app/Contents/MacOS/Libation (see Troubleshooting for macOS).
Alternatively, open the log folder from within Libation: open Settings, and on the first tab click Open log folder.
First and most importantly: Classic and Chardonnay have the exact same features.
Classic is Windows only. Its older 'grey boxes' look has a compact design which allows for more information on the screen. Notably, Classic was written using an older, more mature technology which has built-in support for screenreaders.
Chardonnay is available for Windows, Mac, and Linux. Its modern design has a more open look and feel.
You can use any app which plays m4b files (or mp3 files if you used that setting). Here are just a few ideas. Disclaimer: I have no affiliation with any of these companies:
Self-hosting online:
If you enabled the Request xHE-AAC Codec option in settings, then the audiobook is being downloaded in the xHE-AAC codec which isn't widely supported. You have two options:
For reasons known only to Jeff Bezos and God, amazon and audible brazil handle logins slightly differently. The external browser login option is not possible for Brazil. See this ticket for more details.
Snap keeps per-version folders under ~/snap/libation/<revision>/. After an update, appsettings.json in the new folder may still list "LibationFiles" with an old revision path. Libation then opens the wrong directory and you can see errors about SQLite or migrations even when permissions look fine.
Open appsettings.json next to your running install (often under ~/snap/libation/current/...), set LibationFiles to the Libation data path inside that same revision, save, and launch again. Details: Linux install - Snap, Troubleshooting - Snap, and issue #1776.
Like many countries, amazon gives South Africa it's own amazon site. Unlike many other regions there is not South Africa specific audible site. Use US for your region -- ie: audible.com.
(Not exactly a frequently asked question but it's come up more than once)
Libation cannot download Dolby Atmos or spatial audio from Audible. Full explanation: Spatial Audio, Dolby Atmos, and Widevine DRM.
Libation removed the Request Spatial Audio option in version 13.1.3 (January 2026). Most Dolby Atmos / spatial titles can no longer be downloaded. For many titles, Use Widevine DRM + Request xHE-AAC still gets the highest stereo quality available -- not the Atmos mix.
No. Use Widevine DRM unlocks Request xHE-AAC Codec for higher-bitrate stereo. It does not re-enable spatial/Atmos download. See Does "Use Widevine DRM" download spatial audio? on the spatial audio page.
Libation no longer requests spatial/Atmos from Audible (see Spatial Audio, Dolby Atmos, and Widevine DRM). Books you liberated before 13.1.3 may be E-AC-3 or AC-4; newer downloads are stereo unless you kept older files.
For spatial files you already have, see Playing spatial files you already have and Supported Media Players.