diff --git a/Troubleshooting.md b/Troubleshooting.md
index db161b5..937c81c 100644
--- a/Troubleshooting.md
+++ b/Troubleshooting.md
@@ -38,6 +38,16 @@ In some cases it's necessary to see the database structure to be able to debug t
 
 For this Trilium supports anonymization of the database - you can trigger this in Settings -> Advanced tab.
 
-This will create a copy of your document and remove all sensitive data (currently note titles and note contents and some of the options) while leaving all structure and metadata (e.g. date of last change). After this is done, database is [VACUUMed](https://sqlite.org/lang_vacuum.html) to make sure there's no stale sensitive data in the document file. Resulting file is stored in `trilium-data/anonymized` directory. You can safely attach it with your bug report.
+This will create a copy of your document and remove all sensitive data (currently note titles, contents, revisions, history and some of the options) while leaving all structure and metadata (e.g. date of last change). After this is done, database is [VACUUMed](https://sqlite.org/lang_vacuum.html) to make sure there's no stale sensitive data in the document file. Resulting file is stored in `trilium-data/anonymized` directory. You can safely attach it with your bug report.
 
-Note that [[attributes]] are not cleared because they can contain important metadata for debugging.
\ No newline at end of file
+Note that [[attributes]] are not cleared because they can contain important metadata for debugging.
+
+#### Command line anonymization
+
+If the database is corrupted in a way which prevents Trilium to start up, you won't be able to trigger the anonymization from the UI. For such a case, anonymization is also available from command line:
+
+```
+node src/anonymize.js
+```
+
+This needs to be executed in the directory with Trilium source files, for desktop builds this in in `resources/app` directory.
\ No newline at end of file