Everything about the reMarkable Paper Tablet

User Tools

Site Tools




SSH Access

reMarkable have kindly enabled ssh access to the device by default (version >= when connected to your computer by USB.

As this is the Linux superuser account, you are strongly recommended to make backups.

Finding the Password and IP Address

The SSH password and your device IP Addresses can be found in the settings menu.

  • Settings > About > Copyrights and licenses > General information (scroll down)

From >

  • Settings > Help > Copyrights and licenses > General information (scroll down)

Connecting via SSH (Linux/Mac OSX)

Open a terminal (OSX: Apps > iTerm) and enter this command.

ssh root@remarkable

Then enter your reMarkable password. The password will not be shown as you type it.

Connecting via SSH (Windows)

Download an SSH client, like PuTTY.

Under “Host Name (or IP address)” enter


and hit enter. Then enter your reMarkable password. The password will not be shown as you type it.

Connecting via SFTP

Download and open your FTP program.

Create a new SFTP connection (the S is important don't setup a FTP connection) using the following settings:

  • Host: remarkable
  • Username: root
  • Password: your password
  • Port: 22

Optional but recommended:

Remote path/External folder: /usr/share/remarkable/templates


Host alias in .ssh/config

You can set up an alias that's easier to remember by adding the following lines to the .ssh/config file on your computer:

host remarkable
        User root

Setting up ssh-keys

The reMarkable uses dropbear (via busybox) for its ssh server and supports ssh keys (definitely rsa, as there have been some issues with ed25519 SHA256 keys). By doing so, you can save yourself from entering the random password in the future.

On your host machine, generate a ssh-key if you haven't done so already

$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/chronos/user/.ssh/id_rsa): 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/chronos/user/.ssh/id_rsa.
Your public key has been saved in /home/chronos/user/.ssh/
The key fingerprint is:
SHA256:kONWRVsc4pHeO/ObKieTqJO2A6ZdqY5Zv2v+70SaVD0 chronos@localhost
The key's randomart image is:
+---[RSA 2048]----+
|         .=oo.   |
|       . o.*.    |
|      + ..+.E    |
|     . + .. ..   |
|      o.S .  .   |
|    o.o. +  +    |
|   +.+ .o... +   |
|  .+o.* ..= . .. |
|  o..+BO.oo=..o. |

With ssh-copy-id

To authorize your host machine on the reMarkable using ssh-copy-id

$ ssh-copy-id root@
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/chronos/user/.ssh/"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@'s password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh 'root@'"
and check to make sure that only the key(s) you wanted were added.

The reMarkable should be accessible to the host machine without providing a password.

Note that on some flavors of Linux (notably, Fedora 33 and later) you may need to specifically allow ssh-rsa keys, by adding the following to the file /etc/ssh/ssh_config

PubkeyAcceptedKeyTypes +ssh-rsa

Without ssh-copy-id

To copy and authorize your ssh keys without ssh-copy, begin by creating a .ssh directory on your reMarkable

remarkable: ~/ mkdir /home/root/.ssh

On your host machine, proceed by appending your host key to the devices authentication list

$ cat ~/.ssh/ | ssh root@ "cat >> .ssh/authorized_keys"

NOTE: If you are on a Windows host you can use the following command:

type %HOMEPATH%\.ssh\ | ssh root@ "cat >> .ssh/authorized_keys"

On your reMarkable, set the access rights of the .ssh directory to read-only

remarkable: ~/ chmod -R og-rwx /home/root/.ssh

The reMarkable should be accessible to the host machine without providing a password.

Making Backups

As the easiest option, reMarkable offers a cloud sync service to back up your content - you can use this if you want. Restarting the reMarkable will fix most sync problems if you encounter them during an initial sync. Otherwise, or in addition to this, you should back up your files locally.

Much of this comes from Eeems' blog post about working on the Toltec repository:

First, make a backup folder somewhere:

mkdir -p remarkable-backup/files

Then you probably want to back up at least the following, and perhaps more if you intend to change other files. You may want to make sure you're connecting over USB instead of WiFi (you will be using USB if you followed the above examples), for faster transfers.

# all your content (this will likely take the longest, and could be up to 8GB of data)
scp -r root@remarkable:~/.local/share/remarkable/xochitl/ remarkable-backup/files/

# your configuration file, which also contains your ssh password
scp root@remarkable:~/.config/remarkable/xochitl.conf remarkable-backup/

# the xochitl binary, if you plan on replacing or modifying it in any way
scp root@remarkable:/usr/bin/xochitl remarkable-backup/

Fedora 33

Fedora 33 introduced a new stronger crypto policy which is incompatible with reMarkable's dropbear configuration.

Add an ssh config entry to


like this to work around it.

Host remarkable
  HostName <your-ip>
  User root
  PubkeyAcceptedKeyTypes +ssh-rsa

Ubuntu 20.04

If ssh over usb times out and won't connect, it might be the computer don't detect the correct ip address

Set up a static connection for the USB Ethernet interface with this properties:


This can be achived by entering the Network Manager. Go to settings, choose Network and scroll down to the USB Ethernet section and click the clog wheel next to it, and chose IPv4 tab. swich from Automatic (DHCP) to Manual and enter the values above this text. Reconnect the usb cable and try to ssh again.

Might need to reboot both the reMarkable and the computer if the reMarkable don't show up.

This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information
tech/ssh.txt · Last modified: 2021/03/17 14:40 by mjervis