Software for the reMarkable tablet

Table of Contents

Author Professor Eric S Fraga (
Last modification 2019-09-13 17:19:48


A collection of scripts, mostly, for processing reMarkable tablet documents, both notebooks and annotated PDF documents, on Linux. Use any of these scripts at your own risk; although the author uses these frequently, there is no guarantee that they will work for you.

The mystery (frustration really) for me is that why is it that so many companies use Linux for their products but then provide little or no support for customers that use Linux on their desktop or laptop computers? The scripts here are my attempt to make the best use of the tablet with Linux.

Version 34 (2019-09-13T16:20:23Z).

This script uploads PDF documents to the tablet directly. It creates a set of files that describe a document on the tablet and copies them directly to the xochitl directory on the tablet.

A document on the tablet is represented by a number of individual files and directories in the xochitl directory. These are summarized in this table:

extension type description
  directory annotations will be stored here
.cache directory not sure but empty initially
.content file information including uuids for each page
.highlights directory not sure but empty initially
.metadata file name, dates, type
.pagedata file list of templates, one per page
.pdf file the actual PDF uploaded
.textconversion directory for converted annotations; empty initially
.thumbnails directory 362x512 pixel jpeg, one per page in document
    numbered 0, 1, …, n-1

The script implemented here creates all these files and directories directly in the tablet's xochitl directory with uuids generated using the uuidgen tool on Linux. As there is no description of the actual expected content of some of the data files to be found, I have guessed what the content should be. As a result, this script should be use with care as I am not entirely sure that there are no side effects. My limited testing has not identified any issues but I will take no responsibility for any damage using this script may cause to your tablet!

The script is used as follows:

sshfs root@remarkable.wifi.ip.address ~/remarkable
cd <to where your PDF files may be> PDFfile1.pdf [PDFfile2.pdf ...]
fusermount -u ~/remarkable

The assumptions are that your reMarkable tablet is on the local network and accessible via ssh and that you have created the suitable mount point (~/remarkable in the example above).

default parameter settings

The REMARKABLE environment variable will be used to determine where to copy the files for the PDF document the user wishes to upload. This scripts assumes that the tablet's full file system (root, aka /) has been mounted at this point.


get PDF file information

The tablet documents need to know how many pages there are in any PDF document. We use the pdfinfo tool, from the poppler-utils Debian package, to extract this information. The pdfseparate tool from this package will also be used later on to extract the individual pages from the PDF document.

for pdf in $*
    if [ -f ${pdf} ]; then
        n=$(pdfinfo ${pdf} | grep '^Pages' | awk '{print $2}')
        name=$(basename ${pdf} .pdf)
        date="$(date +%s)000"
        echo Uploading PDF document ${name} with ${n} pages, date ${date}
        temp=$(mktemp --directory rm.XXXXX)
        echo Resulting documents in ${temp}

generate uuid for new tablet document

All files in the xochitl directory of the tablet are based on UUID (universally unique identifier) names. We create one such uuid for this new document and, later, we will also create uuids for each of the pages in the document.

The script also creates a temporary directory on the host system. All the files necessary for the tablet to define a document will be placed here and copied to the tablet at the end of the script. This part of the script prepares the actual PDF document for copying by placing it in the temporary directory with the correct name.

echo Creating $uuid document directories.
mkdir ${dest}
mkdir ${dest}.{cache,highlights,textconversion,thumbnails}
cp ${pdf} ${dest}.pdf

content file

The content file specifies the uuids for each of the pages in the document. We create these uuids here. The values for all the other parameters have been taken from an example document I uploaded using the traditional method (i.e. the Android application, in my case). It could be that some of these parameter values should be different in some cases but I have not yet run into any problems. I would welcome any feedback that says otherwise, of course!

cat > ${dest}.content <<EOF
    "extraMetadata": {
    "fileType": "pdf",
    "fontName": "",
    "lastOpenedPage": 0,
    "lineHeight": -1,
    "margins": 100,
    "orientation": "portrait",
echo '    "pageCount":' ${n}',' >> ${dest}.content
echo '    "pages": [' >> ${dest}.content
while [ ${page} -le ${n} ]
    if [ ${page} -ne ${n} ]
        echo '        "'${pageuuid}'",' >> ${dest}.content
        echo '        "'${pageuuid}'"' >> ${dest}.content
cat >> ${dest}.content <<EOF
    "textScale": 1,
    "transform": {
        "m11": 1,
        "m12": 0,
        "m13": 0,
        "m21": 0,
        "m22": 1,
        "m23": 0,
        "m31": 0,
        "m32": 0,
        "m33": 1

metadata file

The important bits of information in this file, as near as I can tell, are the last modification time and the actual name of the document. I am not entirely sure what the other parameters mean except for synced which we specify as false.

cat > ${dest}.metadata <<EOF
    "deleted": false,
echo '    "lastModified": "'${date}'",' >> ${dest}.metadata 
cat >> ${dest}.metadata <<EOF
    "metadatamodified": false,
    "modified": false,
    "parent": "",
    "pinned": false,
    "synced": false,
    "type": "DocumentType",
    "version": 1,
echo '    "visibleName": "'${name}'"' >> ${dest}.metadata 
echo '}' >> ${dest}.metadata 

pagedata file

The pagedata file contains one line per page. On each line is the template used. By default, a freshly uploaded PDF document would always (I assume) have a Blank template. It would be interesting to make the template used optional as I can imagine cases where, for instance, a grid template would be good to impose.

touch ${dest}.pagedata
while [ ${page} -le ${n} ]
    echo Blank >> ${dest}.pagedata


Each page in the document has a corresponding thumbnail, a small jpeg image. I do not know if these would be generated automatically by the tablet but it is relatively straightforward to generate these at this point. I have observed that some thumbnails get regenerated on the tablet in any case. Note that the pages are numbered from 0 upwards but the pdfseparate tool used to extract the individual pages numbers from 1. The image creation is done using the convert tool from the ImageMagick (imagemagick-6 to be precise) Debian package.

pdfseparate ${pdf} ${dest}.thumbnails/%d.pdf
while [ $page -lt $n ]
    convert ${dest}.thumbnails/$((page+1)).pdf -monochrome -scale 362x512 ${dest}.thumbnails/${page}.jpg
    rm ${dest}.thumbnails/$((page+1)).pdf

copy files to the tablet

At this point, all the necessary files and directories have been created within the ${temp} directory. We now copy these to the tablet. The assumption is that the tablet's file system has been mounted onto this system, probably using sshfs. The location is defined above in the environment variable $REMARKABLE.

( cd ${temp} ; tar cf - . | \
      (cd ${REMARKABLE}/home/root/.local/share/remarkable/xochitl/ ; tar xvf - ))

clean up

Remove the temporary files created.

rm -rf ${temp}

end of if and loop for processing each file


restart xochitl

Once all the files have been created and copied over, we ask the reMarkable tablet to restart the graphical interface, i.e. xochitl. There may be a faster, more efficient way of telling the tablet that there is a new file there but I have not found it yet. Any suggestions would be more than welcome. The script does allow uploading more than one file and only when all have been uploaded is the graphical interface restarted.

This part of the script requires that we log in directly, as root, on the tablet to be able to restart the graphical interface.

ssh root@remarkablewifi systemctl restart xochitl

Convert a remarkable notebook or annotated PDF document to PDF suitable for viewing and/or printing, with colour annotations. This code assumes version 1.7.x of the reMarkable system, the version that introduced the ability to move pages around. The script is here. It relies on an awk script, getpageuuids.awk.

An example of the result for an annotated PDF document:


Usage: UUID

where the UUID argument is the uuid of the document to process, without any extension. The script assumes that the associated files, e.g. uuid.pagedata etc., will be available. For instance, if you have the following files in your current directory,


then f13a0e9c-9c64-4a0f-9cd5-af40c902bb95

will decode the .rm files in the f13a0e9c-9c64-4a0f-9cd5-af40c902bb95 directory and use these to overlay the pages found in the f13a0e9c-9c64-4a0f-9cd5-af40c902bb95.pdf document, creating at the end a document /tmp/f13a0e9c-9c64-4a0f-9cd5-af40c902bb95_annotated.pdf.

There are two scenarios: the first is a notebook file which consists solely of what the user has drawn/written using the stylus. The second is where an existing PDF document has been annotated. In either case, we first process the *.rm files which have the drawn/written aspects. Then, if a PDF file exists, these are overlaid on that file.

This script uses a number of other software components:

  1., originally from, used to convert the reMarkable's data recorded when using the stylus to write or draw to an svg graphic.
  2. inkscape, used to convert the svg graphic to PDF.
  3. pdfinfo from the poppler-utils Debian package, used to determine the orientation and geometry of an existing PDF document that will be overlaid with annotations.
  4. pdftk, used to overlay one PDF on top of another.
  5. gs from the ghostscript Debian package, used to rewrite the final PDF to take up much less space. This is particularly useful (necessary?) when annotating PDF documents created using Microsoft's Word package. As an example, a 277 page document with annotations on approximately 1/3 of the pages led to a final document almost 1 GB in size; after processing via gs, the final document was 22 MB in size. The compromise is that the resulting PDF targets display on a screen and hence is at a lower density than would be appropriate for printing in many cases.

All of these, except the first, are standard packages that can be installed on a Debian system easily. The first is available from the author of this script as it has been modified compared with what is available on the 'net.

revision history for

List of revisions to the shell script:

11. 2020-06-23T16:01:13Z  fixed script due to changes in inkscape's arguments for PDF export
10. 2019-06-08T22:43:08Z  clean up after finishing the conversion
 9. 2019-06-07T23:05:57Z  added link for PDF compression web site
 8. 2019-06-07T22:50:10Z  use gs to compress the PDF pages
 7. 2019-06-07T22:34:07Z  placed annotated PDF document in /tmp directly
 6. 2019-06-07T22:07:09Z  annotated document must include non-annotated pages
 5. 2019-06-07T21:50:28Z  conversion works for notebooks and annotated documents
 4. 2019-06-07T21:38:48Z  overlaying annotations on PDF document works
 3. 2019-06-07T13:23:42Z  conversion makes use of templates
 2. 2019-06-07T13:12:44Z  pages successfully converted to SVG
 1. 2019-05-29T10:57:25Z  started writing the script

List the documents in the xochilt directory of the tablet. The resulting script is here.


This function extracts the document's name from the metadata file. The argument is the uuid document metadata file.

function getmetadataname {
    # echo "Looking for document name in $1"
    grep visibleName $1 | sed -e 's/.*": "//' -e 's/",*$//' -e 's/ /./g'


Recursively traverse the required uuid files to build up the full name of the document whose uuid has been passed to this function.

function getfullname {
    documentname=$(getmetadataname ${meta})
    # echo Document name is $documentname
    # the document may be in a folder.  Use the recursive function defined
    # above to extra a full path to the destination folder
    parentuuid=$(grep parent $meta \
                     | sed -e 's/.*": "//' -e 's/",*$//' -e 's/ /./g' )
    while [ "$parentuuid" != "" ] 
        # echo ".. found folder uuid = $parentuuid"
        directoryname=$(getmetadataname ${xochitl}/${parentuuid}.metadata)
        # echo ".. with name $documentname"
        # move up a folder
        parentuuid=$(grep parent "${xochitl}/${parentuuid}.metadata" \
                         | sed -e 's/.*": "//' -e 's/",*$//' -e 's/ /./g' )
    # echo "back in main, folders = $folders"
    echo ${destination}${documentname}

main block

For each document in the xochitl directory, output the uuid and the full name of the document.

for metadata in $(find ${xochitl} -name '*.metadata')
    uuid=$(basename ${metadata} .metadata)
    # check to see if this is a file or a directory (Collection)
    type=$(grep type ${metadata} | sed -e 's/^.*": "//' -e 's/",.*$//' )
    # echo 'Checking type of file: ' ${metadata} 'is of type' ${type}
    if [ "${type}" == "DocumentType" ]
        fullname=$(getfullname ${xochitl} ${uuid})
        lastchange=$(grep lastModified ${metadata} | sed  's/^.*"\([0-9]\{10\}\).*$/\1/')
        date=$(date --date="@${lastchange}" +%Y%m%d-%H:%M:%S)
        echo ${uuid} ${date} ${fullname}


./ ~/xochitl | sort -k 2 -r

Testing code which will be used to create the reMarkable Emacs mode:

 (shell-command-to-string "./ ~/xochitl | sort -k 2 -r")

reMarkable Emacs mode


This section implements a major mode for the Emacs system which provides an interface to the documents on the tablet. The mode presents all the documents (both notebooks and PDF) in a human friendly way (I hope) and allows the user to select any to convert to a screen friendly PDF using the scripts defined above. The mode depends on the script defined above and available here.

The inspiration for this mode was this presentation.

The mode is defined in remarkable.el.

The typical usage is:

  1. copy the xochitl directory from the tablet to your local system. I use scp for this. You can, however, direct the mode to work with the tablet directory if you have mounted the tablet's file system on your own but this is significantlly slower. Customize the remarkable-xochitl-directory Emacs variable with the actual location on your system.
  2. load the Emacs file. This is what I do:

    (push "where you downloaded remarkable.el" 'load-path)
    (require 'remarkable)
  3. invoke the command provided in Emacs: M-x remarkable RET and the table view of all your documents in the xochitl directory will be presented:


    where some entries have been redacted. The entries have been sorted by date with most recent first; the S key allows you to sort on either column and in both ascending and descending order.

  4. The tabulated-list-mode provides a number of key bindings; type ? to see these. The remarkable-mode adds 2 key bindings to the defaults ones:
    display the uuid of the entry in the mini-buffer below the window.
    convert, if necessary, the document to PDF and view the PDF within Emacs. This works for both reMarkable notebooks and annotated PDF documents.

custom variables

xochitl directory

The custom variables include the directory where the tablet documents can be found. This could be the tablet's own directory if, for instance, the tablet's file system were mounted on this system, or it may be a copy of such.

(defcustom remarkable-xochitl-directory
  "Directory containing the files from the reMarkable tablet.  This should either be a link to the /home/root/.local/share/remarkable/xochitl directory or to a copy of that."
  :type 'string
  :group 'reMarkable)

rmlist script

(defcustom remarkable-rmlist-script "~/s/remarkable/software/"
  "Where the script for listing the files in the xochitl directory is found."
  :type 'string
  :group 'reMarkable)

rmconvert script

(defcustom remarkable-rmconvert-script "~/s/remarkable/software/"
  "Where the script for converting a reMarkable tablet notebook into a PDF file suitable for viewing on the screen.  Also used for creating an annotated version of a PDF document."
  :type 'string
  :group 'reMarkable)

get the list of documents on the tablet

The argument to the method is the directory where all the files on the tablet are found. In practice, for me, this will be a directory on the local system which has been created by copying all the contents of the /home/root/.local/share/remarkable/xochitl directory from the tablet.

(defun remarkable--get-documents (dir)
  (mapcar (lambda (x) (split-string x " "))
           (shell-command-to-string (concat remarkable-rmlist-script " " dir " | sort -k 2 -r")) "\n")))

convert selected document to PDF and view

(defun remarkable--convert-document-and-view (uuid)
  (let* ((uuid (tabulated-list-get-id))
         (pdf (concat remarkable-xochitl-directory "/" uuid "_annotated.pdf"))
         (tmp (concat "/tmp/" uuid "_annotated.pdf")))
    (when (or (not (file-exists-p pdf))
               (concat remarkable-xochitl-directory "/" uuid ".content")
      (message "Converting %s to PDF.  Please wait..." uuid)
      (shell-command (concat "(cd " remarkable-xochitl-directory "; "
                             remarkable-rmconvert-script " " uuid "; "
                             "mv " tmp " " pdf ")"))
      (message "... conversion complete.")
    (find-file pdf)))

define a map for local bindings

(defvar remarkable-mode-map
  (let ((map (make-sparse-keymap)))
    (define-key map (kbd "i") '(lambda () (interactive) (message "uuid = %s" (tabulated-list-get-id))))
    (define-key map (kbd "v") '(lambda () (interactive) (remarkable--convert-document-and-view (tabulated-list-get-id))))

define the derived mode

The mode derives from the tabulated-list-mode which presents a table view into the tablet:

(define-derived-mode remarkable-mode tabulated-list-mode "reMarkable"
  "A mode for viewing documents on the reMarkable tablet."
  (with-demoted-errors "reMarkable mode error: %s"
    (let ((columns [("Date" 18 t) ("Document name" 61 t)])
          (rows (mapcar (lambda (x)
                          (list (car x) (vconcat (cdr x))))
                        (remarkable--get-documents remarkable-xochitl-directory))))
      (setq tabulated-list-format columns)
      (setq tabulated-list-entries rows)

(provide 'remarkable)

define a command to start the mode

Create a buffer (or switch to an existing one) and start up the mode defined above:

(defun remarkable ()
  (switch-to-buffer "*reMarkable*")
  (goto-char (point-min)))

Document revision history

Recent changes to this document:

34. 2019-09-13T16:20:23Z  added direct link to script
33. 2019-09-13T16:18:36Z  Comment on the need to have ssh root access to tablet
32. 2019-09-13T16:17:03Z  link to local copy of Tao Peng's CSS
31. 2019-09-13T15:29:13Z  descriptive text for all the pdf2rm script components written
30. 2019-09-13T08:56:44Z  defined REMARKABLE environment variable
29. 2019-09-11T16:31:38Z  copy files over to tablet, clean up, and restart xochitl
28. 2019-09-11T14:45:54Z  fixed visible name entry
27. 2019-09-11T12:24:26Z  all other files created and some minor errors corrected
26. 2019-09-11T11:44:21Z  pagedata file created
25. 2019-09-11T11:41:52Z  started writing script
24. 2019-08-02T13:56:28Z  move point to start when loaded
23. 2019-08-02T12:13:34Z  fixed internal link for HTML export
22. 2019-08-02T12:11:12Z  very minor change in wording
21. 2019-08-01T11:14:31Z  viewing PDF saves PDF for later views as well
20. 2019-08-01T10:31:46Z  added usage information for the remarkable Emacs mode
19. 2019-08-01T10:03:54Z  added and remarkable.el to list of files to upload
18. 2019-08-01T09:55:11Z  remarkable mode view command works
17. 2019-08-01T09:36:13Z  changed column widths for remarkable table display
16. 2019-08-01T09:32:14Z  renamed internal functions and enabled 'i' binding for uuid details
15. 2019-07-31T21:35:39Z  added provide statement to enable require for loading remarkable

Author: Professor Eric S Fraga

Created: 2020-08-28 Fri 15:53