If you're considering a reMarkable 2 and your biggest concern is transferring your notes to your computer, it's understandable to feel a bit lost: the official website makes it seem simple, while some reviews find it confusing . In reality, the process can be very straightforward or a bit more technical, depending on the method you choose and whether or not you want to pay for the Connect subscription.
In this article, you'll find a straightforward overview of all the practical options for exporting, importing, and syncing annotations : from USB cables and local web interfaces, through official apps and cloud services like Google Drive, to more advanced workflows using SSH on Linux and Git repositories. I also compare the situation with other e-readers (like Kobo with Calibre), where extracting annotations is feasible, but restoring them to the device is often a different story.
How exporting actually works in reMarkable 2
The reMarkable 2 saves each page of your notebooks in its own format (.rm) with layers of digital ink. From there, you can obtain copies in standard formats (PDF, PNG, or similar) or sync with official applications. The key question is whether you want a faithful "dump" for archiving or if you want an editable copy back and forth with the same handwritten ink.
When you export to PDF or image, you get a very faithful visual representation of your handwriting and sketches. It looks just like it did on the tablet, but those strokes are no longer editable as reMarkable ink: the PDF remains "flat" to the outside world. To preserve the original editableness, you need to keep the notebook's internal files within the device's ecosystem.
The most convenient "official" way is usually to use the reMarkable apps (desktop/mobile) and the associated cloud service. Synchronization is seamless there, but some of those advanced integrations are tied to the Connect subscription . Without Connect, you still have viable wired options using the USB web interface, although you lose direct access to external cloud services.
In addition to the official methods, there are advanced methods available with Linux: SSH connections, scp transfers, and automated Git/GitLab processes . These are not officially supported, may change with updates, and carry risks, but many technical users employ them to maintain complete control.
Exporting without a Connect account: what you can and can't do
If you don't want to pay a monthly fee, the most useful option is wired access via the USB web interface . You connect the reMarkable to your computer via USB, open your browser, and go to the local address displayed by the device itself (a minimalist page). From there, you can upload and download documents without going through the cloud.
This method lets you bring PDFs and EPUBs onto your tablet to read and annotate, and then export copies. For archiving and sharing, PDF is the most practical option because it looks the same on any device. If you need individual page images, that's also possible. The important thing here is that you do everything locally, without external accounts or services.
What are the limitations without Connect? You won't have direct access to services like Google Drive, Dropbox, or OneDrive from the official interface, nor premium features such as certain automations or advanced conversion. But for basic DIY transfers , USB drives are a lifesaver.
Another issue is the editable "back and forth" of the ink. If you export to PDF, you can then re-import that PDF to the reMarkable and continue writing over it, but you won't be able to edit the original strokes as native ink . The PDF remains in the background, and your new notes are added on top. To maintain full editableity, it would be necessary to move the internal file system and metadata, something that isn't trivial for the average user.
Finally, a pragmatic reminder: no Connect doesn't mean no options . If your data stream is local (USB), you can organize your backups in folders on your computer, use third-party software to convert or rename files, and create your own backups without relying on external services.
With Connect: integrations with Google Drive and other cloud services
If you're considering paying for the Connect subscription, the main advantage is the convenience of the integrations . From reMarkable itself or its apps, you can send and organize documents to services like Google Drive, Dropbox, or OneDrive, eliminating manual steps and automating part of the workflow.
This is ideal if your goal is to have a file in the cloud accessible from any device without worrying about cables or local sessions. Similarly, sharing PDF notebooks with colleagues or clients becomes a matter of a few taps, with less friction than the USB method.
Keep in mind that Connect doesn't magically convert .rm files into reversible edits outside of the tablet. Editable fidelity remains an internal issue : anything output as a PDF/image will be "flattened." The subscription solves the logistics (integrations, automation, availability), not the nature of the formats.
If you work with teams or clients who require documentation in the corporate cloud, a subscription can save you time. But if you prefer control and don't mind a more manual, wired workflow , you might not need it. Your decision should be based on how much automation you want and how critical direct access to Drive/Dropbox/OneDrive is.
Regarding common concerns like "are they hiding something?", the reality is less conspiratorial: Connect focuses on convenience and integrations . Without it, you can export and make local backups without issue; with it, you do it more conveniently and with access to cloud services.
Export formats and writing “fidelity”
This is one of the key questions: can I export my notes "as is" and re-import them to continue editing the same ink? The short answer is that when you export to PDF or image, the strokes are fixed . Visually they look perfect, but they are no longer editable reMarkable ink.
So there's no going back and forth? It depends on what you mean by going back and forth. If your goal is to resume work by writing over it, then yes: you re-import the PDF and continue annotating . If what you want is to modify the original strokes as if it were the same notebook, that goes beyond simple and enters advanced territory (moving .rm files, metadata, internal structure). It's not something the average user will want—or should—touch.
This situation isn't unique to reMarkable: many digital ink ecosystems work the same way. Standard exchange formats prioritize viewing . Full editable functionality is usually limited to the native system. Therefore, it's wise to decide whether your need is to "export for reading or sharing" (PDF) or "keep it editable on the device."
If your project requires preserving the original ink as editable off-device, you'll run into practical limitations. In that case, consider a hybrid workflow : keep the live sketchbook in reMarkable, export PDF versions for archiving/sharing, and, if you need layers, manage duplicates directly on the tablet.
For projects involving sketches, architectural plans, or formulas, PDF works very well as a frozen, "ready to send" format. The display quality is excellent , and the recipient receives exactly what you see, without any risk of incompatibility.
Linux, SSH and Git: options for advanced users
If you use Ubuntu (or any Linux distribution) and want full control, you can connect to the reMarkable via SSH using a USB cable. This is an unofficial access method for advanced users and may change with updates. Use it at your own risk: tampering with the system without proper knowledge can cause problems.
The general idea is that, when connected via USB, the device exposes a local network interface. With the appropriate credentials, you can open an SSH session and transfer files using scp/rsync . This allows you to automate dumps, batch renames, or even run scripts that package material into your project structure.
What does this have to do with Git and GitLab? Very directly. If your laptop workflow uses a Git repository, you can download your exports to a versioned folder and commit/push to GitLab. You can even schedule scripts that, when the reMarkable is connected, copy new PDFs to your notes repository, create branches for each project, or tag them by date.
An important point: even though SSH gives you access to internal structures, modifying low-level notebooks (.rm files and metadata) to force an editable back-and-forth is neither convenient nor secure. If something gets corrupted, you could lose your work. The sensible approach is to use SSH to automate backups, exports, and archiving, not to perform open-heart surgery on the system.
If you prefer not to use SSH, you can follow the same approach with the USB web interface: download the PDFs to your repo folder , commit, and push. It's an extra manual step, but it's robust, clear, and doesn't rely on external integrations.
What about Google Drive without Connect? Practical alternatives
If your goal is to have all your notes in Google Drive but you don't want to use Google Connect, you can use a local "bridge." For example: download the PDFs via USB to a folder on your desktop Drive (a synced folder), and let the Drive client upload everything in the background.
Another option is to set up workflows using synchronization tools in Linux (rclone, inotify + scripts) so that every time new files arrive in a folder , they are uploaded to Drive or a shared folder on the computer. It's not as convenient as the direct button on the reMarkable, but once set up, it works like a charm.
If you work with teams, consider using consistent naming conventions: project_date_version.pdf . This way, even if you move files manually, you'll always know what each one is. And if you use Git in addition to Drive, you'll have a history and redundant backups.
In operational summary: without Connect, you manage the "glue" between reMarkable and the cloud . This could be a Drive client, an rclone script, or Git as a version control backend. The advantage is that you're not dependent on subscription changes; the cost is spending some time setting it up.
Useful comparison: Kobo annotations with Calibre
For reference, many Kobo users use Calibre with the Kobo Utilities plugin to manage annotations. When they finish a book, they connect their e-reader, select the file in their library, and, using "Copy annotation for Selected Book," retrieve all the notes and highlights along with their location in the EPUB . They then paste this content into a custom column in Calibre, where it becomes indexed for searches.
This is very practical in one direction: from the e-reader to your Calibre library . But the reverse process (transferring extended annotations back to the reader) becomes much more complicated. It would involve editing the device's SQL database, which is not only inconvenient but also risky.
Why mention this in an article about reMarkable? Because it illustrates a common reality: extracting and archiving annotations is usually easy; reinjecting them as native text is not . Something similar happens with reMarkable: exporting to PDF/image is a breeze; bringing that same ink back as editable text is not so simple.
If you're coming from Kobo/Calibre and are already used to that "one-way" workflow, you probably won't mind using the reMarkable with PDF exports and keeping the editing live on the device. It's the cleanest way and the least troublesome in the long run.
Can I just use a USB cable... and that's it?
Yes. If you don't want subscriptions or to rely on services, the USB cable and local web interface cover the essentials : importing PDFs/EPUBs for reading and annotating, and exporting your notebooks as PDFs for archiving on your computer.
If you ever need to move it to the cloud, you can do so from your computer (Drive, Dropbox, OneDrive, GitLab, etc.). The process isn't as seamless as "just click and go" as with Connect , but it's robust, private, and you won't be left stranded if the terms of service change.
For minimal professional use (meeting notes, internal documentation, teaching), this method is more than sufficient. The key is consistency with your backups and organization : folders for each project, dates in the file names, and, if you're up for it, a Git repository for historical records.
Should I return the device if I don't pay for Connect?
The decision depends on your ideal workflow. If you want the tablet to natively integrate with Google Drive/Dropbox/OneDrive and save you steps, Connect will be valuable. If you prioritize local control, privacy, and paying €0, you're not tied to that : you can go about your life without any problems using USB.
For needs like "having copies in Drive" or "uploading to GitLab," there are subscription-free solutions: a synchronized Drive folder on your PC, upload scripts, or Git repositories where you version your PDFs. All of these work equally well with local exports.
If you're also a Linux user and interested in automation, you'll be able to implement a fine-tuned workflow without Connect . The only thing you won't easily achieve (with or without Connect) is the editable back-and-forth of ink in native format externally; all ecosystems have limitations in this area.
My general recommendation: if your priority is writing comfortably and archiving without hassle, don't return the reMarkable for this reason . If you were looking for native Drive integrations and shortcuts "without having to touch anything," try Connect for a while and decide based on actual usefulness.
Quick FAQ
Is the handwriting preserved when exporting? Visually, yes: the PDF exactly reflects your strokes . But those strokes are not editable like native ink outside of the device.
Can I re-import and continue editing exactly the same thing? You can re-import a PDF and add new annotation layers on top . Editing the original strokes as native ink is not straightforward for the average user.
Does it work with Google Drive without Connect? Directly from the tablet, no. But you can export via USB and let your PC sync to Drive . It's an extra step, but very reliable.
Can I connect via SSH from Ubuntu? Technically, yes: it's an unofficial method for advanced users , subject to change and with risks. Use it to automate backups, not for low-level manipulation of notebooks.
Can I upload it to a GitLab repository? Of course: export via USB (or scripts), save it to a repo folder, and commit and push just like any other project . You can even automate it with hooks or cron.
Although the official website sometimes sounds "too friendly" and some reviews sound "too harsh," the reality is more balanced: exporting from reMarkable to your computer is easy if you accept PDF/image as the output format ; the challenge isn't getting the notes out, but rather trying to edit them externally as if they were still native ink. With USB drives, official apps, or even your own Linux scripts, you can set up a robust workflow for saving, sharing, and versioning your notebooks without necessarily relying on a subscription.