Day One to Obsidian Converter
Convert your Day One journal entries into Markdown files compatible with Obsidian.
Features
- Complete Data Migration: Transfers all text, images, and metadata (including creation dates) from Day One entries.
- Markdown Formatting: Converts Day One entries into Markdown format, making them compatible with Obsidian and other Markdown editors.
- Tag Support: Migrates all tags from Day One, allowing for easy categorization and search within Obsidian.
- Image Embedding: Automatically transfers and embeds any images from Day One entries into the Markdown files.
Quick Start
Install uv package manager and run in the unpacked Day One export directory:
uvx dayone-to-obsidian run
Usage
Follow these steps for conversion:
-
Prepare Your Day One Export: Export your Day One journal entries to a JSON file or directory containing multiple JSON files following the manual.
-
Run the Conversion: Open a terminal or command prompt and execute the CLI with the appropriate options. The command structure is as follows:
uvx dayone-to-obsidian run --json /path/to/your/dayone_export.json --target /path/to/target_directory [--force] [--tag-prefix=prefix] [--tag=tag1] [--tag=tag2]
--json: Path to your Day One export JSON file or directory. If not specified, it defaults to the current directory.--target: Path to the directory where converted Markdown files will be saved. By default, a new folder is created in the current directory.--force: Force the overwriting of existing journal folder.--tag-prefix: Prefix for tags, allowing customization of how tags are formatted in the converted files.--tag: Additional tag(s) to add to all entries. This option can be repeated to include multiple tags.--help: Display the help message.
Example command:
uvx dayone-to-obsidian run --json ./DayOneExport/Journal.json --target ./ObsidianNotes --tag-prefix=DayOne/ --tag=Imported --tag=Journal
This command specifies a Day One JSON export file, sets the target directory for the converted Markdown files, adds a prefix to all tags, and includes additional tags for each entry.
-
Import to Obsidian: Once the conversion process is complete, manually move the generated Markdown files to your Obsidian vault directory.
Support
If you encounter any issues or have suggestions for improvements, please open an issue in this GitHub repository.
License
This project is licensed under the MIT License. See the LICENSE file for details.
1 maintainer
Metadata
1 maintainer
Release files for dayone-to-obsidian 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dayone_to_obsidian-0.6.1.tar.gz | 2.9 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dayone_to_obsidian-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 MB
Release files / dayone_to_obsidian-0.6.1.tar.gz
| Download URL | dayone_to_obsidian-0.6.1.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f55715f01402e5b1e194e811b12e4433e0bcd0ded47acbcc18d317a7c11acf85
|
|
BLAKE2b-256 checksum How to use checksums |
6d602ab0a062959e61476308b82fcc13cce8e83fa374dd093b828dfcdf1ba891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / dayone_to_obsidian-0.6.1-py3-none-any.whl
| Download URL | dayone_to_obsidian-0.6.1-py3-none-any.whl |
|---|---|
| Size | 15.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b632a157e2873b89e091b545f8d0685b195c6f2fc66920ef0f64a188a4b5ea3e
|
|
BLAKE2b-256 checksum How to use checksums |
1b7ce52296bb5a9bec2a195b237554242be39534ef12ac08c16f2fdb23560b77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logSecurity for dayone-to-obsidian 0.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dayone_to_obsidian-0.6.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
