Why Native DWG Still Needs Desktop CAD

ToolComb’s DWG Viewer chooses transparency: detect native binary DWG, show what is missing, reuse DXF parsing when the bytes are exchange-compatible, and disable PNG export when nothing drawable appeared. That is less flashy than a spinner that ends in an empty canvas - and faster for teams who need a yes/no before midnight.

This guide explains why native DWG still belongs on desktop CAD for production, when browser preview is still enough, and how DXF export bridges the gap. Pair with DXF vs DWG in the browser and How to view DXF online.

What DWG is (and why the web struggles)

DWG stores geometry, blocks, layouts, object enablers, and version-specific features in a binary tuned for AutoCAD-family apps. Releases differ: compression, custom objects, proxy graphics, and external references multiply test matrices.

A complete in-browser DWG pipeline typically requires one of:

Approach	Tradeoff
LibreDWG / WASM port	GPL and completeness gaps on newer objects
ODA or commercial SDK	License cost and bundle size
Cloud convert API	Upload privacy, retention, and vendor lock-in
Fake “viewer”	Blank or partial canvas sold as success

ToolComb does not ship the last row. Users deserve a message, not a silent failure on R2018+ custom entities.

DXF is the intentional escape hatch: exchange format, parser-friendly, lossy for some DWG-only features but good enough for 2D review when exported cleanly.

What ToolComb’s DWG page actually does

Upload .dwg or .dxf to DWG Viewer.

Path A - drawable content (often DXF inside)
Same 2D canvas as DXF Viewer: LINE, LWPOLYLINE, CIRCLE, ARC, TEXT. Layer toggles, Fit to view, Export PNG.

Path B - native binary DWG without a drawable DXF payload
Status card explains the limit. Guidance toward Save As DXF in desktop CAD. No fake preview.

Entity scope matches DXF v1 - not hatches, dimensions, splines, or INSERT explosions. Native DWG that would only show through those features still will not show them after DXF export unless they flatten to supported types.

When browser preview is enough

• Quick extent check before driving to site
• Layer name sanity when layers map to supported entities
• PM approval when outlines + TEXT carry the decision
• Vendor ping: “This .dwg did not parse - please send DXF”

When the decision is permit stamp, CNC toolpath from hatches, or legal area measurement, stop at the browser.

When desktop CAD (or ODA-backed tools) is mandatory

• Native DWG is the contractual deliverable and must round-trip
• Dynamic blocks, parametric constraints, 3D solids
• XREF assemblies and sheet sets
• Certified dimensions on drawings
• Custom object enablers from vertical products (Civil, MEP)

Export DXF for web review; keep authoritative DWG in the PDM vault.

Practical export workflow for senders

In AutoCAD-class tools:

1. Purge unused layers and blocks when possible.
2. Model space geometry for review (not only paper layouts).
3. Save As DXF - note version if the recipient’s parser is old.
4. Optionally explode view-only blocks that must appear in a simple viewer.
5. Send both DWG (contract) and DXF (web QA) when policies allow.

Recipients open DXF on DXF Viewer or .dwg on DWG Viewer when testing compatibility.

Annotator: not a DWG escape hatch

DWG/DXF Annotator helps when you already loaded a drawable DXF - add redlines, export PNG or minimal DXF. It does not decode opaque native DWG into editable geometry. Calling it full DWG edit would mislead.

Privacy vs cloud “free DWG online”

Many convert-and-view sites require upload. For facility security, unreleased product, or personally identifying survey, that copy is a data event. Browser-local DXF after your desktop export keeps bytes on the machine you control - still not zero risk (malware, shoulder surfing), but narrower than a stranger’s S3 bucket.

ToolComb’s claim is narrow: no application-server decode for the canvas you see. Pages load over HTTPS; treat shared kiosks like any sensitive document.

Common misconceptions

“It opens in ShareCAD so browser DWG is solved.”
Third-party engines vary; many upload. Read their retention policy.

“DWG and DXF are the same if the icon looks similar.”
Extension ≠ bytes. Always read the viewer status.

“PNG export proves the drawing is complete.”
PNG proves what drew - subset entities only.

“ToolComb is AutoCAD online.”
No Autodesk affiliation. Open-source DXF parsing + honest DWG detection.

Related tools

• DWG Viewer - .dwg upload with limits
• DXF Viewer - dedicated .dxf
• DWG/DXF Annotator - redlines
• CAD Tools - hub listing

The honest bottom line

Open dwg in browser limits are format and licensing limits, not laziness. Native DWG for production stays on desktop CAD (or enterprise viewers you pay for). DXF export unlocks private, local 2D preview on ToolComb for the LINE / LWPOLYLINE / CIRCLE / ARC / TEXT subset. Use the DWG Viewer to learn which side your file landed on - then act on the message instead of fighting a blank canvas.