diff --git a/Backups.md b/Backups.md
index cb0f970..7f91f9d 100644
--- a/Backups.md
+++ b/Backups.md
@@ -34,3 +34,11 @@ Example: ``TWNK-KDEY-MTWT-EVGS-DRDB-KVTW``
   * I haven't found studies targetting this special use case in computer science, but some target similar ones, but only considering long term memory:
     * [2015, Jun Ho Huh et al.: On the Memorability of System-generated PINs: Can Chunking Help?](http://lersse-dl.ece.ubc.ca/record/304/files/soups2015-final110.pdf)
     * [2006, Deborah S. Carstens, Linda C. Malone, Pamela McCauley-Bell: Applying Chunking Theory in Organizational Password Guidelines](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.97.2782&rep=rep1&type=pdf)
+
+## Saved as a file
+* When saving backups as a file ASCII armor MUST be used and a special header MUST be added: ``BackupVersion: 2``
+* This way implementations can check if it is a backup and a special dialog for entering backup codes can be shown instead of a dialog with single text fields for entering passwords.
+* The header does not automate anything, it poses no additional security threat.
+
+## Saved in other storages
+* When saving in other storages, such as private XMPP storages, ASCII armor is not required. Thus, the ASCII armor header can not be used. To show a special dialog, the implementation must know that the file came from a special storage and is a backup
\ No newline at end of file