An honest list of what exists, and what is coming. Tell us what matters most and we will build that first.
Next: heavier in-browser engines
Still on your device, but they need bigger libraries such as WebAssembly encryption and OCR.
Encrypt a PDF so it needs a password.
Needs a PDF engine that can write encrypted files. Planned as a WebAssembly add-on.
Unlock a PDF you have the password for.
Needs a decryption engine (WebAssembly). Planned alongside Add a password.
Make scanned pages searchable and copyable.
Needs an in-browser OCR engine and language packs, which are large downloads.
Draw or type a signature and place it.
Needs a drawing pad and drag-to-place editor. For now, use “Logo or image stamp” with a picture of your signature.
Type into fillable form fields.
Needs a field editor. For now, use “Write on a PDF” to place text.
Later: conversions that need a server
Accurate Office conversions do not run well in a browser. If we build these, we will say clearly whenever a file is sent off your device.
Convert .docx documents to PDF.
Accurate conversion needs a document engine that does not run well in a browser. It would run on a server, and we would tell you clearly when a file leaves your device.
Get an editable .docx from a PDF.
Needs server-side layout analysis. Planned with a clear notice that files are sent to be converted.
Spreadsheets to tidy PDFs.
Needs a spreadsheet layout engine, so it would run on a server.
Pull tables out into a spreadsheet.
Table detection is hard to do reliably in the browser. Planned on a server.
Slides to PDF.
Needs a presentation renderer, so it would run on a server.
Turn HTML or a web page into a PDF.
Needs a full browser engine to lay out pages, so it would run on a server.