| Feature | Local Processing | Upload Required |
|---|---|---|
| Files stay on your device | Yes — always | No — uploaded to remote server |
| Patient data transmitted | None | Yes — to provider's infrastructure |
| Internet required to view | No (after initial page load) | Yes |
| Time to start viewing | Instant — no upload wait | Depends on file size and bandwidth |
| Cost | Free | Often subscription-based |
| Account required to view | No | Often required |
| Server data retention | None — data never stored | Provider retains uploaded data |
| Works offline | Yes | No |
Why Local Processing Protects Your Patients
Your DICOM files never leave your device. No pixels, patient metadata, or DICOM tags are transmitted to any server at any step.
View and edit DICOM files without creating an account or providing any personal information.
No upload wait time. Files open immediately from your local filesystem — performance depends on your device, not server load.
Once the page loads, view and analyse DICOM studies without an internet connection. Ideal for low-connectivity clinical environments.
Frequently Asked Questions
Yes. Files are read from your device using the browser File API and processed in-browser using WebGL. No network request containing your imaging data is initiated at any point in the workflow.
Nothing is retained. DICOM files are processed in browser memory only. When you close the tab, the data is gone. We store no patient data on our servers.
Because no PHI is transmitted to our servers, the architecture supports your HIPAA posture. Consult your compliance officer to evaluate suitability for your specific clinical environment.
Upload-based viewers send your files to a remote server for processing. Your patient data leaves your device and is processed on infrastructure you do not control. Local processing keeps all data on your machine throughout the entire workflow.