rmdocs
A cli tool to convert .rm, .rmdoc and the xochitl folder of the reMarkable 2 to PDFs.
It aims to reproduce reMarkable 2 output as faithfully as possible.
Usage
- Convert a single
.rmfile usingrmdocs my_page.rm [destination folder].[destination folder]defaults to current folder. - Convert a single
.rmdocfile usingrmdocs my_document.rmdoc [destination folder].[destination folder]defaults to current folder. - Convert a folder containing a collection of
.rmor.rmdoc(can't be mixed) usingrmdocs [source folder] [destination folder].[destination folder]is required. - Convert the
xochitlfolder at/home/root/.local/share/remarkable/xochitl/on the remarkable usingrmdocs [source folder] [destination folder].[destination folder]is required.
If you have compatibility or assertions issues, please refer to below.
Installation
- Install pipx
- Install
libcairo2. For instance, on debian based system useapt install libcairo2. - Install
rmdocsviapipx install rmdocs
Compatibility
This software is only compatible with page version 6, and I do not plan on making it support other page version. For non-compatible pages a warning text will be shown instead of your strokes. Going to each of these pages individually and drawing (even if removing afterward) makes the reMarkable updates the page to v6.
Additionally, as there is no official API for reMarkable file structure, many assertion are made based on the files
available while developing this software. The output of the software will show them as AssertionException. Please
consider opening an issue when you have such errors.
Acknowledgment, contributions and license
This uses rmscene, and part of svg creation is based of rmc.
This software is mainly released under the MIT license. Certains files (from rmc) regarding the svg creation are under LGPL.
Contributions are welcomed :).
Metadata
Release files for rmdocs 3.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rmdocs-3.5.3.tar.gz | 20.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rmdocs-3.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.3 kB
Release files / rmdocs-3.5.3.tar.gz
| Download URL | rmdocs-3.5.3.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87ed07cf252359848443b5c5b804fbf2286784e29dce7a557d3e2d300e681b89
|
|
BLAKE2b-256 checksum How to use checksums |
59cab3571bed5b1931615edc03b5262cab869df0be71adc990541c60a299a201
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 21, 2026.
Transparency logRelease files / rmdocs-3.5.3-py3-none-any.whl
| Download URL | rmdocs-3.5.3-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cd08a1d491fdd2cc00d370545a8ae37fbf79e09b1ba54e0cf0082e599d0ed39
|
|
BLAKE2b-256 checksum How to use checksums |
38aaea1fbfe9bd2f940b91361cb62795f0909f039e3c4c2353df8d7e8fae652f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 21, 2026.
Transparency log