How to import Markdown notes into Scrinium
By the Scrinium team · Published 13 November 2026
If you already have Markdown notes, you can add them to an unlocked Scrinium vault from Settings. The import creates new encrypted notes and leaves the existing notes in that vault in place.
This guide is written by the Scrinium team. It covers individual text files and Scrinium’s own plaintext JSON export, rather than a full migration of another app’s database.
The short answer
Open Settings, then Data, then Import notes. Choose Markdown / .txt / plaintext and select the files. Review the titles, choose Import, then Click again to confirm. Start with a few files and check their contents before importing a large collection.
Prepare the files
The file picker accepts .md, .markdown, .mdown, .txt and .text files, plus a Scrinium plaintext JSON export. Select files directly; there is no ZIP extraction or folder-tree migration in this workflow.
For an individual text file, the filename without its extension becomes the title. Its text becomes the note body, with an empty folder and no imported tags. YAML front matter stays in the body; it is not converted into folder or tag metadata. Keep a separate copy of your source files.
Import and check a small sample
- Unlock the destination vault and open Settings.
- Open Data, choose Import notes, then Markdown / .txt / plaintext.
- Select a few files. Review the displayed titles and note count; choose Cancel if you selected the wrong files.
- Choose Import, then Click again to confirm. Open the resulting notes and check their full text, lists and code blocks.
Check images, links and folder names
Importing a Markdown file does not upload the images or attachments it refers to. Relative paths and another app’s internal links may not resolve. Keep those original files separately and check any links you rely on after import.
Scrinium JSON can carry titles, folders, tags and timestamps in addition to the body. A text file’s directory path is not preserved as a folder tree. Use the organization guide to arrange imported notes.
Avoid duplicates and use the right JSON option
Each import creates new note IDs. Importing the same file twice can create two copies; it does not update a note just because the title matches. Import a large collection in deliberate batches and check the count and contents after each batch.
An encrypted backup belongs under Encrypted backup (restore vault), which replaces the current local vault. It is not a plaintext import. The backup and restore guide explains the difference. Sync imported notes only after checking the result.
Questions about this workflow
Does importing Markdown replace my existing vault?
No. Plaintext import adds new encrypted notes to the unlocked vault. Encrypted backup restoration is a separate operation that replaces the local vault.
Will front matter and local image files be migrated?
Front matter remains part of the note body; it is not parsed into folder or tag metadata. Referenced image files are not uploaded by importing the Markdown file.
Will repeating an import update the old notes?
No. Imports use new note IDs, so repeating the import can create duplicates even when filenames or titles match.