autokey2espanso
Convert AutoKey phrase entries into Espanso YAML configuration.
Why?
If you are migrating from AutoKey to Espanso, this tool converts your existing phrase entries automatically.
It reads matching .json and .txt pairs and generates a valid Espanso matches: configuration.
Requirements
- Python 3.8+
Installation
Install with pip
pip install autokey2espanso
Or clone the repository:
git clone https://github.com/johannjdk/autokey2espanso.git
cd autokey2espanso
pip install .
Or run directly:
python3 autokey2espanso/cli.py <directory>
Usage
Basic usage (prints YAML to stdout):
autokey2espanso /path/to/autokey/phrases
Write output to file:
autokey2espanso /path/to/autokey/phrases -o espanso.yml
Verbose mode:
autokey2espanso /path/to/autokey/phrases -o espanso.yml -v
Word mode (-w / --wordmode):
autokey2espanso /path/to/autokey/phrases -o espanso.yml -w
Custom prefix (-p / --prefix):
autokey2espanso /path/to/autokey/phrases -p ":" -o espanso.yml
When enabled, the prefix will be added before each trigger. If omitted, triggers are taken 1:1 from AutoKey.
When word mode is enabled, each entry will include:
word: true
This is useful for triggers that should only match entire words in Espanso.
How it works
For each entry, both files must exist:
Example.json
Example.txt
The first abbreviation inside the JSON file becomes the Espanso trigger. With optional prefix:
"abbreviations": ["hello"]
Becomes with -p ":":
matches:
- trigger: ":hello"
replace: |
Hello World!
Or 1:1 (no prefix):
matches:
- trigger: "hello"
replace: |
Hello World!
If word mode is enabled:
matches:
- trigger: ":hello"
word: true
replace: |
Hello World!
License
MIT
Metadata
Release files for autokey2espanso 1.1.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 | Provenance | |
|---|---|---|---|---|
| autokey2espanso-1.1.0.tar.gz | 3.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autokey2espanso-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / autokey2espanso-1.1.0.tar.gz
| Download URL | autokey2espanso-1.1.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
529048d1affa51211dabe7931a4ddcd3322d98333bdc26cd6dc26c03962b5a84
|
|
BLAKE2b-256 checksum How to use checksums |
d26d3fc0c309cd9c7360b1cc7b25e3fe815179605aedc16dce786c0ae4979305
|
| 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 Sep 23, 2026.
Transparency logRelease files / autokey2espanso-1.1.0-py3-none-any.whl
| Download URL | autokey2espanso-1.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7b4196f176dd79bf589708e91860b58e80b502a94000a2e32d5df393ecf710a
|
|
BLAKE2b-256 checksum How to use checksums |
dc4e231be92c62fdff4b0c8c3bbbec612e8c45be549330a323a9c1948959848f
|
| 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 Sep 23, 2026.
Transparency logSecurity for autokey2espanso 1.1.0
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 autokey2espanso-1.1.0.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 Sep 23, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.