Forms and records that stay on the device
Intake forms, referrals and claims often contain personal data. DocuVerse opens and edits them in the browser, so nothing leaves the device unless your application sends it.
Full name
A. Rahman
Date of birth
14 / 03 / 1987
Allergies
3
formats in one viewer: PDF, Word and Excel
20+
markup, signing and page tools
0
uploads to a third-party service
MIT
licence: free for commercial use
Use cases
Where DocuVerse fits in healthcare & insurance
Complete intake forms
Patients type, tick and sign on the Fill and Sign tab, on a tablet or desktop.
Learn moreComments · 3
$ docuverse docx2pdf proposal.docx proposal.pdfwrote proposal.pdf (14 pages)$ docuverse search proposal.pdf "renewal"page 3: … the renewal date is 1 March …page 9: … renewal fees are listed in …$ docuverse annotate proposal.pdf out.pdf 0 '{"type":"Stamp","icon":"Approved"}'annotation 42 added · saved out.pdf
Process on your servers
Flatten, render or extract text from submitted forms with Node.js or .NET.
Learn moreThe workflow
From first draft to the final file
- 1
Open the form
The intake form opens in the browser on a tablet or desktop.
- 2
Complete
The patient types, ticks and signs on the Fill and Sign tab.
Submit
Your app decides where the signed PDF goes: nothing leaves the device before that.
Capabilities
What teams need, and how DocuVerse covers it
Local processing
Documents are processed inside the browser; none is sent to a conversion service.
Complete the form
Text, check marks, dates and signatures placed directly on the page.
Readable on any device
The same viewer in desktop and mobile browsers, or inside a .NET application.
Server-side when you want it
Render, flatten or extract text on your own servers with Node.js or .NET.
Privacy and security
Documents stay where your users are
Forms with personal data are completed in the browser. They leave the device only when your application submits them.
- Documents open inside the browser, on the user’s device
- Encrypted PDFs open with the user or owner password
- Your application chooses what is saved, and where
only when your app sends it
Build it
This workflow in a few lines
The same engine behind JavaScript and .NET, so the result is identical wherever it runs.
const viewer = await createViewer(element, { document: '/forms/patient-intake.pdf', initialTab: 'sign', // start on Fill and Sign disabledElements: ['download'], // saving goes through your app only onSave: async (bytes) => { await fetch('/api/intake', { method: 'POST', body: bytes }); },});The SDKs
Client side, server side, and soon mobile
Private by design
Documents are processed where your users are: in their browser, or on your servers.
Same result everywhere
Every SDK gives the same result, so a file looks and saves the same on every platform.
Free under MIT
Every feature, unlimited users and servers, no licence keys or per-document fees.
Other industries
See it with your own documents
Free under the MIT licence, for PDF, Word and Excel, in the browser and on your servers.
Comments · 3