Markor
Markor 2.16.1 is an open-source Android editor for plain text, Markdown, todo.txt and local notes, with preview, sharing and quick actions built around ordinary files.
What Markor does
Markor edits ordinary text files directly instead of locking notes into a proprietary database. It supports Markdown, todo.txt, plain text, preview, sharing and quick actions, making the working directory part of the data model.
Storage and synchronization boundaries
The actual location of a note depends on the selected workspace and Android storage permission. Cloud or peer synchronization requires a separate file tool such as Syncthing or a drive client; two devices editing the same file at once can create conflicts.
APK channels and signatures
F-Droid, project releases and other stores can use different signing keys. A new APK cannot be assumed to replace an installation from another channel. Back up notes and settings before changing the source and use one consistent update channel afterward.
File access and privacy
Android scoped storage limits access to private application directories. Grant only the selected folders through the system file picker, keep versions or snapshots for important notes and inspect local paths before sharing a document.
Maintenance note
Review date: 2026-08-23. The page was checked against Markor 2.16.1, Android storage behavior, Markdown and todo.txt workflows, synchronization conflicts and APK signing boundaries.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Markor to this cloud drive
Baidu Netdisk
Save Markor to this cloud drive
Markor 2.16.1 installation and local Markdown notes guide
Install the APK from one trusted channel, choose a workspace, create Markdown and todo.txt files, preview the result and verify a separate backup or synchronization copy.
Before you start
- Use Android 4.3 or later and account for device-specific storage and file-picker behavior.
- Choose F-Droid, a project release or another trusted channel for long-term updates instead of switching signatures repeatedly.
- Decide whether the notes directory will be synchronized and prepare an independent backup before editing important files.
Installation steps
- 01
Verify package and signing channel
Check that the APK belongs to the Markor project and reports version 2.16.1. Allow installation from the selected source only temporarily, then disable that permission.
- 02
Grant access to the notes folder
Use the system file picker to select the dedicated workspace and grant only the required folder scope rather than broad storage access.
- 03
Set workspace and file formats
Choose directories for quick notes, tasks and documents, then check Markdown, todo.txt or plain-text defaults, encoding and line endings.
Quick start
- 01
Create a Markdown note
Create an md file with a heading, list and link, switch to preview and check rendering. Avoid file names with characters that the selected sync tool cannot handle.
- 02
Build a todo.txt list
Create a todo.txt file and organize tasks by priority, project and context, confirming that sorting or completion changes only the intended text.
- 03
Verify backup or synchronization
Close the editor, let the selected file tool copy the workspace and open the result on another device or in a backup directory to check content and encoding.
Usage tips
- Plain files are portable, but deletion and overwrite act directly on the file. Use version history, snapshots or independent backups for important directories.
- Preview and sharing can hand content to another application. Check local paths, metadata and private text before sharing.
- Grant storage and network access only when the feature needs it, then retest the workflow after revoking an unused permission.
Troubleshooting and uninstall
Why is a file garbled in another application?
Use UTF-8 consistently, check line endings and confirm that the synchronization tool did not treat the text as a binary file or convert its encoding. Test a copy before conversion.
Why does an APK update report a signature mismatch?
The old and new packages came from different signing channels. Back up documents and settings, verify the new source and install it as a deliberate channel change instead of forcing an overwrite.
- Back up text and settingsCopy notes, task lists and attachment directories, then open several files in another editor. Shared files may remain after uninstall, but keep an explicit backup.
- Uninstall and revoke accessRemove Markor, clear selected cache and shortcuts, disable temporary installation permission and confirm that synchronization tools no longer monitor an obsolete directory.
Frequently asked questions
Where does Markor store notes?
Markor edits files in the workspace selected by the user. The exact path depends on Android storage permission and the file-picker choice; synchronization needs a separate file tool.
Can the F-Droid build replace an APK from another source directly?
Not in every case. Different signing keys can block an in-place update. Back up notes and settings, then uninstall the old source and install the trusted new channel deliberately.
Why can Android 11 or later not show a directory?
Scoped storage limits access to private directories. Use the system file picker to grant the required folder and avoid escalating to broad or unknown storage permissions.