Boox Google Drive Sync: The Working Setup (Note Air 2)

The frame

How Boox Google Drive sync actually works

Boox google drive sync is built into the Notes and NeoReader apps on Note Air 2 and the rest of the current Boox lineup. The device authenticates against your Google account via OAuth, you pick which Note folders to mirror, and the device exports each note as a PDF (or PNG, configurable) to a Boox-named folder inside Drive. That export runs on a schedule and on a manual trigger; the schedule is conservative by design to keep battery life intact.

What confuses most setups is that the sync is one-way by default. Boox writes to Drive; Drive does not write back. Notes you edit on Drive (in the browser, on another device) will not flow back into the Notes app on the device. If you want true two-way sync, you need the third-party Drive Android client and a manual mapping that we cover in the troubleshooting section below. The companion Onyx Boox help center documents the official sync as one-way export.

Setup

The working Boox Google Drive setup steps

Confirm the device is on a current firmware.

Settings → About → System update. Older firmware versions on Note Air 2 had a known OAuth bug that throws an auth failure on the third refresh. Updating clears it. If the device is already current, skip this step but verify the version number first.

ii.

Open the Notes app and go to the cloud-sync tab.

Notes → Settings (gear icon top-right) → Cloud sync. The list includes OneDrive, Dropbox, and Google Drive. Google Drive is the last entry by default; tap it.

iii.

Authenticate with the OAuth flow, in the device browser.

The device launches the OAuth flow in its built-in browser. Log in with the Google account you want to receive the synced files. Grant the Drive scope when prompted. If the auth fails, see the gotchas section; the most common cause is a stale token from a prior installation.

iv.

Pick the source folders, not the whole notes library.

The default is to sync every folder. Override that; pick only the folders you actually want in Drive. Each note exports as a separate PDF and writes a checkpoint file. A device with 200 notes and the default selection will hammer Drive on every sync; a device with 20 selected notes will not.

Set the schedule and test with a manual trigger.

Schedule options are Wi-Fi only, on-change, or every N hours. Wi-Fi only is the right default for battery. Once the schedule is set, hit the manual sync button once; the first run takes the longest, and seeing it succeed once confirms the OAuth scope and folder mapping before you walk away.

What syncs

What Boox syncs to Google Drive and what it does not

Note PDFs: Yes, exported per-note on each sync
Note PNGs: Optional, configurable per folder
Tags and metadata: Partial; not all tag systems flow through to Drive filenames
NeoReader annotations on PDFs: Yes, flattened into the exported PDF
Highlighted books: Yes, with annotations flattened
Library sideloads: No; only files you have annotated
App data: No; sync is Notes and NeoReader only

The shape of the sync is “what you annotated, not what you stored.” That is the right default for most readers: it keeps Drive clean and makes the export a working backup of your annotation layer rather than a copy of every PDF you sideloaded. If you want full-library backup, sideloads need a separate Drive client or a USB-mounted folder export.

Gotchas

The two gotchas that break most Boox Drive setups

The first gotcha is OAuth scope. The Boox auth flow asks for “Drive” not “Drive file scope only.” If you have previously connected the same Google account to a third-party app that requested a narrower scope, the token can collide. The fix is to revoke the prior token in your Google account permissions page and re-authenticate fresh on the device.

The second gotcha is folder ambiguity. If two Note folders have the same display name (one in a subfolder, one at the root), the sync writes both into the same Drive folder and the later sync overwrites the earlier. The fix is to rename the device-side folders before first sync; the renames stay local to the device and do not affect the Drive target name.

For two-way sync, the working approach is to install the official Google Drive Android client from the device’s Play Store (Boox runs Android), point it at the same target folder, and use the Drive client to push changes from your laptop or browser back into a Boox-watched folder. The Notes app does not natively read external changes; that is by design and unlikely to change soon. For a clean cross-device note workflow we cover the boox templates catalog as the source of the templates that hold up to this sync pattern, and the boox hub for adjacent how-tos.

FAQ

Common questions, answered briefly

Does Boox Note Air 2 sync to Google Drive natively?

Yes. The Notes and NeoReader apps both include Google Drive as a cloud-sync option. The setup lives under Notes → Settings → Cloud sync → Google Drive on current firmware.

Is the sync one-way or two-way?

One-way by default, Boox to Drive. For two-way sync, install the official Google Drive Android client from the Play Store on the device and use it to bridge changes from the browser side back to a Boox-watched folder.

What gets synced exactly?

Notes you select (as PDF or PNG export) and annotated PDFs from NeoReader. Library sideloads and app data do not sync; only the annotation layer does. For full-library backup you need a separate Drive client or a USB-mounted export.

Why does the OAuth keep failing on Boox Drive setup?

Most often a stale token from a prior installation. Revoke the prior Boox token in your Google account permissions page, then re-authenticate fresh on the device. If that fails, update firmware; older Note Air 2 builds had a known auth bug.

Does the sync drain the battery noticeably?

Only if you keep the default folder selection (every note). Selecting a small set of folders and using Wi-Fi-only sync keeps battery drain minimal. The first sync after pairing is the longest; subsequent syncs are quick.

If your edge case isn’t above, drop it in the comments. We update this page when a setup question reshapes the workflow.