Questions people ask

Yes. LEXO is free and open source under the AGPL-3.0-or-later licence. Google Docs OCR is also free to use through your own Google account, so there is no per-page or subscription cost.

The AGPL lets you use LEXO for any purpose, including commercial digitization. If you modify LEXO and distribute it, or offer a modified version to others over a network, the AGPL requires you to share your changes under the same licence. Read the licence for the exact terms.

Partly. Opening files, all PDF tools, extracting text from digital PDFs, proofreading, and exporting work offline. OCR of scans and images uses Google Docs OCR, which needs an internet connection. LEXO is local-first, not a fully offline OCR engine.

The page images you OCR. LEXO uploads each page image to your own Google Drive, Google Docs OCR reads it, LEXO downloads the text, and then deletes the temporary file. Pages you don't OCR, and everything else you do in LEXO, stay on your computer.

No. LEXO requests only the drive.file scope, which gives access only to files LEXO itself created.

No. There is no LEXO account, no LEXO server in the middle, and no telemetry in the app. You use your own Google Cloud OAuth client, and the app talks to Google directly.

Google requires every app that uses Drive to authenticate with an OAuth client. Instead of shipping a shared client, LEXO has you create your own in a free Google Cloud project, which keeps your OCR traffic under your account. It's a one-time, six-step setup.

Because you created the OAuth app yourself and it stays in Testing status. That's expected for personal use. Only the test users you listed can sign in.

Google expires sign-ins for OAuth apps in Testing status after roughly seven days. Run lexo login again; the desktop app offers to sign you in when it needs to.

No billing is needed for this setup. You can ignore free-trial offers in the console.

LEXO doesn't promise a number. Results depend on the scan quality, the typeface, and the layout. Google Docs OCR handles printed Myanmar script well in practice, but you should proofread the output, which is why LEXO shows every page beside its text.

It was typed in a legacy font such as Win Innwa, which draws Burmese on top of ASCII letters. Use Google Docs OCR to read the page visually and get Myanmar Unicode.

No. If a PDF's text layer is Zawgyi-encoded, run Google Docs OCR on it to get standard Unicode from the page image.

LEXO is built and tested for printed text. Google Docs OCR may recognize some handwriting, but it isn't a supported use case.

Burmese is the default. Other languages, including other non-Latin scripts, can work through Google Docs OCR when you pass the right language hint with --lang, but LEXO is tuned for Burmese.

Windows, macOS, and Linux, with Python 3.11, 3.12, or 3.13. LEXO's CI tests all three systems on all three Python versions.

No. Install LEXO with uv, pipx, or pip. One package includes the CLI and the desktop app.

Yes. Batch OCR writes one UTF-8 text file per PDF and skips files already done, so interrupted runs resume.

No. LEXO extracts text page by page. Layout-aware extraction and table structure aren't built in yet.

No. The desktop app edits a working copy. Your original is only replaced if you choose Save.