KeIO
A Python CLI for importing and exporting Google Keep notes to markdown directories.
KeIO stores sync metadata in an HTML comment footer at the bottom of each exported markdown file, enabling conflict detection and incremental syncing.
Fun fact: KeIO stands for "Keep I/O" 😊
Installation
pip install keio
Or with uv:
uv tool install keio
To use the gkeepapi backend (see Authentication below):
pip install "keio[gkeepapi]"
Authentication
KeIO supports two authentication backends. You must pick one; they cannot be mixed.
Option A: Enterprise (official Google Keep API)
[!WARNING] The official Google Keep API is only available to Google Workspace Enterprise users. It will not work with free
@gmail.comaccounts or non-Enterprise Workspace plans.
This backend uses the official REST API with a standard OAuth 2.0 Desktop App flow.
- Go to Google Cloud Console.
- Create or select a Google Cloud project.
- Search for "Google Keep API", open it, and click Enable.
- Search for "Google Auth platform" and open it.
- If no app exists yet, use the setup wizard to create one.
- Open Clients and create a Desktop app OAuth client (or download JSON from an existing one).
- Run setup and login:
keio auth setup --method enterprise --credentials /path/to/credentials.json
keio auth login
References:
Option B: gkeepapi (unofficial, any Google account)
[!WARNING] This backend uses the unofficial gkeepapi library, which reverse-engineers the mobile Google Keep protocol. It can break without notice if Google changes their internal API. Attachment download support is limited.
This backend works with any Google account, including free @gmail.com. Setup requires
obtaining a master token via a Docker one-liner.
Step 1 -- Get an OAuth token cookie:
- Open https://accounts.google.com/EmbeddedSetup in your browser.
- Log in with your Google account and click "I agree". (The page may show a loading screen indefinitely after this; that is expected.)
- Open browser developer tools -> Application -> Cookies.
- Copy the value of the
oauth_tokencookie.
Step 2 -- Get a master token (via Docker):
docker run --rm -it python:3 sh -c '
pip install -q gpsoauth && python3 -c "
import gpsoauth,secrets,json
e=input(\"Email: \")
t=input(\"OAuth token: \")
a=secrets.token_hex(8)
r=gpsoauth.exchange_token(e,t,a)
print(json.dumps({\"email\":e,\"master_token\":r[\"Token\"]}))"'
Step 3 -- Pass the JSON to keio:
You can pass the JSON output directly:
keio auth setup --method gkeepapi --credentials '{"email":"...","master_token":"..."}'
Or save it to a file first:
keio auth setup --method gkeepapi --credentials /path/to/token.json
Then verify:
keio auth login
References:
Other auth commands
keio auth status # Show current method and login state
keio auth logout # Remove cached tokens
Usage
Export
Export your Google Keep notes to a local directory:
keio export /path/to/notes
- Downloads note text, checklists, and attachments.
- Skips locally modified files unless
--forceis used. - Use
--dry-runto preview without writing.
Import
Import markdown files back to Google Keep:
keio import /path/to/notes
- Supports note text and checklist content.
- Uses footer metadata to detect stale local files and avoid conflicts.
- Skips notes whose remote version is newer unless
--forceis used. - Use
--dry-runto preview without creating or replacing notes.
Image upload (--images)
[!IMPORTANT] Neither the official Keep API nor gkeepapi supports uploading attachments programmatically. Export can download images, but import cannot upload them.
The --images flag provides a semi-automated workaround:
keio import /path/to/notes --images
For each note that has local attachments, --images will:
- Create or update the note text in Google Keep as usual.
- Open the note in your browser and the attachment folder in your file explorer.
- Poll the note for up to 5 minutes, waiting for you to drag-and-drop the images into Keep manually.
- Press Enter at any time to skip a note and move on.
This makes it practical to re-attach images in bulk without hunting for each note by hand.
Common flags
| Flag | Applies to | Description |
|---|---|---|
--dry-run |
export, import | Preview changes without writing |
--force |
export, import | Ignore conflict checks and overwrite |
--credentials PATH |
export, import | Override OAuth credentials file |
--images |
import | Assist with manual image upload (see above) |
Development
git clone https://github.com/soldni/keio.git
cd keio
uv sync --extra dev
uv run pytest
License
Apache-2.0
Metadata
Release files for keio 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| keio-0.2.0.tar.gz | 873.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keio-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 903.3 kB
Release files / keio-0.2.0.tar.gz
| Download URL | keio-0.2.0.tar.gz |
|---|---|
| Size | 873.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07f3d3d0cb9e2fa476221101f00742291fb2d0b31ac306f3d86407175165d31e
|
|
BLAKE2b-256 checksum How to use checksums |
f76923c87506d7b93f64ba20404d07f0dca335d7a13edf60af4a438811874e27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 1, 2026.
Transparency logRelease files / keio-0.2.0-py3-none-any.whl
| Download URL | keio-0.2.0-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f66a448f526629bb4c022e6d327c988efa8885c9632564c7010222077b09daa1
|
|
BLAKE2b-256 checksum How to use checksums |
013e9be6ccf0703f7a5f5920c65fa24394e1659c225c9df914cac6117c493d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 1, 2026.
Transparency log