CherryTree
A hierarchical note-taking application for structured text, code snippets, tables, links and attachments stored in an editable notebook tree.
What CherryTree is for
CherryTree organizes notes in a hierarchical tree and can hold formatted text, code snippets, tables, links and attachments. It fits personal knowledge bases, study notes and project records. The notebook is a data set that needs backups and version-aware migration, not just a disposable text editor file.
Keep the tree and attachments together
A note may reference images, files, links or embedded data. Choose a notebook location with stable permissions, avoid scattering attachments across temporary folders and test reopening the notebook after a move before deleting the original.
Use synchronization deliberately
Concurrent edits to a structured notebook can create conflicts or overwrite changes. Prefer one writer at a time or a versioned copy workflow, and keep sensitive notes outside untrusted synchronization services unless their storage and encryption model is understood.
Maintenance note
This page reviews CherryTree hierarchical notes, attachments, code snippets, backups and synchronization boundaries. Content review date: 2026-08-23.
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 CherryTree to this cloud drive
Baidu Netdisk
Save CherryTree to this cloud drive
CherryTree notebook and backup workflow
Create a small notebook tree, add text and a code snippet, attach one harmless file, reopen the notebook from a backup copy and only then migrate larger notes.
Before you start
- Choose a stable notebook directory with enough space for text, attachments and backup copies.
- Decide which notes are sensitive and keep them separate from any shared or synchronized folder.
- Prepare a harmless sample attachment for the first move and recovery test.
Installation steps
- 01
Install and open CherryTree
Install the package for the operating system, launch it and choose a notebook path that is easy to back up and restore.
- 02
Create the notebook tree
Add top-level topics and child nodes, keeping names and hierarchy consistent so later search and export remain understandable.
- 03
Add representative content
Create formatted text, a code snippet, a table and a harmless attachment, then save and close the notebook before reopening it.
Quick start
- 01
Search and link notes
Use the tree and search to locate the sample content, add a local link between related nodes and verify that the target remains valid after reopening.
- 02
Create a backup copy
Close the notebook, copy the complete data set to a separate location and open the copy to verify that attachments and formatting survive.
- 03
Test a migration workflow
Move a copy to the intended new path or device, reopen it, inspect attachments and recent edits, and keep the original until the test is complete.
Usage tips
- Large attachments make backups and synchronization slower; link or archive them deliberately.
- Export or copy a consistent, closed notebook instead of copying files while the application is writing.
- Sensitive notes need their own access, encryption and retention decisions.
Troubleshooting and uninstall
Why is an attachment missing after moving the notebook?
Check whether it was embedded or stored as a relative or absolute external path, then restore the expected directory structure from a closed backup copy.
Why did a synchronized notebook lose an edit?
Stop concurrent writes, compare the last known good copies and merge changes manually or through a versioned workflow instead of repeatedly syncing conflicting files.
- Verify the backupOpen a complete backup copy and confirm that the tree, attachments and recent notes are present before removing the application.
- Uninstall CherryTreeExit the application and uninstall it through the operating system, keeping notebook data and configuration as separate decisions.
Frequently asked questions
Is CherryTree just a folder of text files?
A notebook can include hierarchy, formatting, code, tables and attachments with relationships that should be backed up as a consistent data set.
Can the same notebook be edited on two devices at once?
Concurrent edits can create conflicts or overwrite changes. Prefer one writer at a time or a versioned copy and merge workflow.
What should be checked before deleting the original notebook?
Open the backup copy, inspect recent notes and attachments, and confirm that the intended search, links and formatting remain usable.