When you capture survey data — whether from drone flights, terrestrial LiDAR, or total stations — that data represents real value. It's the foundation of your deliverables, your competitive advantage, and often, your client's confidential project information.
Key Takeaways
- All point cloud processing happens locally on your hardware
- Project files are stored in standard folders you control
- Database is a human-readable JSON file — no proprietary formats
- No telemetry, no usage analytics, no data collection
- Core functionality works offline after license activation
A Conversation About Data Ownership
Where that data lives and who can access it matters. Not because cloud services are bad (they're not), but because different projects have different requirements. Sometimes you need the flexibility of cloud access. Sometimes you need the certainty that your files never leave your network.
Viizor offers both options. This post focuses on what the Desktop version provides for users who prioritize local data control.
How Viizor Desktop Handles Your Files
Let's be specific about what happens when you work with Viizor Desktop.
All Processing Happens on Your Computer
When you load a LAS or LAZ file into Viizor Desktop, the conversion to viewable format happens locally. The PotreeConverter runs on your machine. The Python metadata extractor runs on your machine. The resulting octree files are written to your local drive.
Your point cloud data doesn't travel to any external server for processing. There's no "uploading" step, no cloud queue, no waiting for remote servers to become available.
Project Files Stay on Your Drive
Viizor Desktop stores all project data in a local folder:
This is your data, in folders you control, on storage you own. You can back it up, move it, or delete it without asking anyone's permission.
The Database Is a Simple JSON File
Project metadata, cloud references, and saved configurations are stored in a single JSON file (viizor-data.json). It's human-readable. You can open it in any text editor and see exactly what information Viizor is storing.
There's no hidden database, no encrypted proprietary format, no data that exists only on someone else's server.
What Connects to the Internet (and What Doesn't)
Viizor Desktop does make some external network requests. Here's the complete list:
What Connects
- epsg.io — Coordinate system lookups when searching for EPSG codes
- geodesy.noaa.gov — Geoid height calculations for elevation conversions
- Map tile providers — Satellite imagery for 2D map view
- License validation — Initial activation + periodic checks
What Doesn't Connect
- Your point cloud files are never uploaded
- Your project data is never synchronized
- Your measurements and surfaces stay local
- No telemetry about usage patterns
- No analytics tracking features used
The application doesn't "phone home" with your project information. The network requests that do occur are functional (coordinate lookups, map tiles) rather than data collection.
Why This Matters for Certain Projects
Local processing isn't just a technical preference. For some users, it's a requirement.
Government and Defense Contracts
Many government projects have strict data handling requirements. Survey data for military installations, critical infrastructure, or sensitive facilities often cannot be processed on external servers, regardless of security certifications.
With Viizor Desktop, the data never enters a third-party system. Compliance documentation is simpler because there's no cloud provider to audit.
Client Confidentiality Agreements
Some clients — particularly in mining, energy, or real estate development — require that their site data remain confidential. They may have contractual provisions prohibiting cloud processing of survey data.
Desktop processing means you can truthfully tell clients: "Your data was processed entirely on our internal systems."
Air-Gapped Environments
Certain facilities operate networks with no external internet access. Viizor Desktop can run in these environments (after initial license activation). The core functionality — loading point clouds, creating surfaces, exporting to CAD formats — doesn't require connectivity.
Slow or Unreliable Internet
Not every job site has fiber internet. Field offices, remote locations, and international projects may have limited bandwidth. Processing a 500MB point cloud locally takes the same time whether you have gigabit internet or a cellular hotspot.
The Tradeoffs
Let's be honest about what you give up with local-only processing.
What Local Processing Doesn't Provide
No automatic backup. Your data is as safe as your backup strategy. If your hard drive fails and you don't have backups, your projects are gone.
No multi-device sync. If you work from multiple computers, you'll need to manually transfer project files.
No collaborative editing. Multiple team members can't work on the same project simultaneously. You can share exported files, but real-time collaboration requires a different architecture.
For many users, these tradeoffs are acceptable. For others, cloud-based workflows make more sense. That's why Viizor also offers a web version for users who prefer that model.
Practical Data Management
Some suggestions for users who choose local processing:
Set Up a Backup Routine
The entire Viizor data folder can be backed up with standard tools. Windows File History, manual copies to external drives, or enterprise backup solutions all work. The folder path is predictable and the files are standard formats.
Consider the Project Folder Location
By default, Viizor stores data in AppData. For large projects or team environments, you might want to use a shared network drive or a location that's included in your existing backup infrastructure.
Export Early and Often
LandXML and DXF exports are your insurance policy. Even if something happens to your Viizor installation, the exported files remain usable in any compatible CAD software.
Document Your Coordinate Systems
Since Viizor preserves whatever coordinate system your source data uses, keep records of which EPSG codes apply to which projects. This information lives in the metadata, but external documentation prevents confusion months later.
A Note on the Web Version
Viizor's web version exists for users who want cloud convenience — access from any device, no installation, automatic updates. That's a legitimate choice for many workflows.
This post isn't arguing that cloud processing is wrong. It's explaining what the Desktop version offers for users whose requirements point toward local processing. For a detailed pricing comparison, see Professional Point Cloud Software at a Fair Price.
Both versions produce the same outputs. Both handle the same file formats. The difference is where the processing happens and where the data lives.
Summary
Viizor Desktop provides:
- Local processing: Point clouds are converted on your hardware, not uploaded to external servers
- Local storage: All project data lives in folders you control
- Minimal network dependency: Core functionality works offline after activation
- Transparent data handling: JSON database, standard file formats, no proprietary locks
- No telemetry: The application doesn't collect or transmit usage data
For surveyors and engineers who need to maintain strict control over client data, meet government security requirements, or simply prefer knowing exactly where their files are, the desktop model provides that certainty.
Own Your Software, Own Your Data
One-time purchase. No subscription. No recurring fees. No ongoing relationship required.
$540 One-time payment
Windows 10/11 • No credit card required for trial