Create Nested Note
Daren Wesolowski2 downloadsCreate a folder and a same-named note from the file explorer context menu.
- Overview
- Scorecard
- Updates2
Create a folder and a same-named Markdown note from Obsidian's file explorer context menu.
Features
- Adds Create nested note to the file explorer context menu.
- Creates inside a selected folder or beside a selected file.
- Opens the newly created note automatically.
- Accepts names with or without the
.mdextension. - Prevents invalid filenames and accidental path collisions.
- Works without accounts, network access, telemetry, or external services.
- Supports desktop and mobile versions of Obsidian.
Usage
- Right-click a file or folder in Obsidian's file explorer. On mobile, long-press the item.
- Select Create nested note.
- Enter a name and select Create.
For example, entering about-this-site creates:
about-this-site/
└── about-this-site.md
When invoked on a folder, the new folder is created inside it. When invoked on a file, the new folder is created in that file's parent folder.
Requirements
- Obsidian 1.4.0 or newer
- Desktop or mobile
Installation
Community plugins
Once the plugin is available in Obsidian's Community Plugins directory:
- Open Settings → Community plugins.
- Select Browse and search for Create Nested Note.
- Select Install, then Enable.
Manual installation
Download
main.js,manifest.json, andstyles.cssfrom the latest GitHub release.Create this directory inside your vault:
.obsidian/plugins/create-nested-note/Copy the three downloaded files into that directory.
Reload Obsidian.
Enable Create Nested Note under Settings → Community plugins.
Development
Node.js 20 or newer and npm are required.
npm ci
npm run lint
npm run build
Available scripts:
| Command | Purpose |
|---|---|
npm run dev |
Watch main.ts and rebuild the development bundle. |
npm run lint |
Run ESLint with Obsidian's recommended rules. |
npm run build |
Type-check, minify, and stage the production package. |
npm run package |
Alias for the complete production build. |
npm run deploy -- "<plugin-directory>" |
Copy an existing package into a local vault. |
Production files are staged in dist/.
The included VS Code tasks provide Build production package and Deploy to working vault commands. The deploy task builds first and then updates the working vault installation.
Testing
This project is tested with BrowserStack.
Project structure
.
├── .github/workflows/ci.yml
├── .vscode/tasks.json
├── docs/RELEASING.md
├── scripts/
├── main.ts
├── manifest.json
├── styles.css
└── package.json
Privacy and security
The plugin operates entirely within the active Obsidian vault. It does not make network requests, collect telemetry, display advertisements, require an account, or access files outside the vault.
Contributing
Bug reports and focused pull requests are welcome. See CONTRIBUTING.md for development and validation expectations.
Releasing
Maintainer instructions for GitHub releases and Obsidian Community Plugins submission are in docs/RELEASING.md.
License
Licensed under the MIT License.