Why the major packages are Windows-first
AutoCAD Electrical, EPLAN Electric P8, most regional equivalents and nearly every panel-building add-on are Windows applications. The reasons are historical and self-reinforcing.
The feature set grew around Windows APIs. OLE embedding, COM automation, Windows-only printing stacks, registry-based licensing and third-party libraries that were never ported. Rewriting the core to be cross-platform is a multi-year project with no new revenue attached.
The customer base is Windows. Electrical contractors, panel shops and design offices standardise on Windows because the software they need runs there. Vendors see no commercial reason to fund a Mac port that would serve a small slice of users.
The ecosystem is Windows. Manufacturer symbol libraries, DXF-based add-ins, reporting tools and template packs are distributed as Windows installers. Even a hypothetical native port would inherit a pile of dependencies.
EPLAN states supported operating systems explicitly in its system requirements; Autodesk publishes separate Windows and macOS requirements for AutoCAD, and the Electrical toolset is a Windows product. That is the practical situation, and no amount of forum optimism changes it.
The workarounds, ranked by how often they work
| Approach | What you get | Where it fails |
|---|---|---|
| Parallels / VMware Fusion on Apple silicon | A real Windows desktop, good performance | Licence cost for Windows and the CAD seat, RAM pressure, USB dongles and network licences may not pass through |
| Boot Camp | Native Windows performance | Intel Macs only; not available on Apple silicon |
| Wine / CrossOver | No Windows licence, sometimes works | Installers, .NET dependencies, printing and licensing break unpredictably; not supportable in a firm |
| Remote desktop to a Windows machine | Full software, centralised files | Needs a reliable link and a server; latency on large drawings; useless on site |
| Native Linux or macOS tools | QElectroTech, LibreCAD, FreeCAD run natively | No panel schedules, no load calculations, no standard checks |
| Browser-based CAD | Runs on any modern browser and OS | Requires a connection; not a full DWG editor |
The pattern is clear. Every option that gives you the full commercial feature set requires a Windows machine somewhere — locally in a virtual machine, or remotely on a server. Every option that runs natively on macOS or Linux gives up engineering features.
What actually breaks in a virtual machine
Virtualisation is the standard answer for Mac users who need AutoCAD Electrical, and it works well enough that many firms use it. The failures are specific and worth knowing before you commit.
RAM. A Windows VM wants 8 GB minimum, and CAD wants more. On a 16 GB laptop that leaves little for macOS, and swapping makes a large drawing feel broken rather than slow.
Graphics. Virtual GPUs handle 2D drafting acceptably. Anything with heavy hatching, large raster underlays or 3D piping struggles.
Licensing. Network licences, hardware dongles and machine-bound activations are the usual casualties. Check with your vendor before assuming a VM is licensed — many allow it, some do not, and the licence agreement is the authority.
Printing and plotting. Plot styles and paper sizes configured on Windows may not match what the VM exposes. Verify a real PDF at real scale before a submission, not after.
File paths and fonts. Shared folders, Unicode paths and missing SHX fonts produce the classic missing-text drawing. It is fixable, but it costs an afternoon the first time.
None of this makes virtualisation wrong. It makes it a Windows solution with a macOS front end, which is a different claim from "CAD on a Mac".
What a browser tool changes
A browser-based tool removes the operating system from the question. If the browser runs, the tool runs — on macOS, on Linux, on a Chromebook, on a site laptop, on a client's machine during a meeting.
The practical consequences go beyond convenience:
- No installation or update cycle. The version you open is the current one; nobody is on last year's build.
- No licence server to maintain for the design environment itself, and no dongle to lose.
- The same file on every device. Open the project on the office desktop, review it on a laptop, show it on a phone. No copy, no "final_v3".
- Sharing is a link, not an export. A colleague or a client can look at the panel schedule without installing anything.
That last point is underrated. A large share of the friction in small electrical firms is not drawing — it is getting a document in front of someone who does not have the software.
GorkyCAD runs entirely in the browser: import a plan or PDF survey, place walls and rooms, add sockets and luminaires, generate the single-line diagram and the panel schedule, run the checks and export PDF, DXF, XLSX or IFC. The demo needs no account and no install, which is the fastest way to see whether the workflow fits how you actually work.
The honest limits
A browser tool is not a desktop CAD replacement, and the limits should be stated plainly.
It is not an offline tool. No connection, no project. If you work on site in a basement with no signal, a browser tool will not help you; download the documents you need beforehand. This is the single biggest constraint and it should decide the question for anyone whose work happens in plant rooms.
DWG support is limited. DXF import and export work well for 2D exchange. DWG is a proprietary format with a long version history; expect viewing and conversion rather than full round-trip editing of complex drawings with dynamic blocks, annotative scaling and custom objects. If your clients send DWG with heavy customisation, keep a desktop tool for that step.
No PLC or control-schematic design. GorkyCAD is built for building electrical installations — plans, circuits, distribution boards, calculations, documentation. Ladder logic, terminal-strip engineering and cross-referenced control schematics belong in EPLAN or a dedicated schematic editor. If that is your main deliverable, this is not your tool.
Not a BIM authoring platform. IFC export exists; full architectural coordination with clash detection does not.
Browser limits are real. Very large raster underlays and thousand-object drawings are bounded by the tab's memory. For ordinary apartment and small commercial projects this is not noticeable; for a 40-storey riser diagram, check before you commit.
Print scale must be verified. As with any tool, plot a test sheet and measure a known dimension with a ruler before issuing a drawing.
A setup that works for a Mac or Linux user
If you need the full commercial toolset occasionally and want to work on your own machine the rest of the time, the split is straightforward.
- Keep one Windows environment — a VM on the Mac, or a remote desktop — for DWG editing and control schematics. Use it for what it is for, not as your daily environment.
- Do the plan, circuits, panel and calculations in the browser. This is where the model matters and where the OS has never helped anyone.
- Export at the end. PDF for issue, DXF for whoever insists on CAD, XLSX for the estimator.
- Test on the smallest machine you own. If the tool is usable on a five-year-old laptop, it will be usable on the office desktop.
For Linux users the argument is even simpler: there is no realistic path to running AutoCAD Electrical natively, and Wine is a maintenance hobby rather than a production strategy. A browser tool is the only way to get a model-based electrical workflow on the same machine you already use.
Start with the live demo, then check pricing for what the free tier includes and what Pro adds; the documentation lists supported import and export formats in detail. If you are also weighing open source options, the open source electrical CAD breakdown covers what those tools do and do not produce.
Sources
- Autodesk AutoCAD product and system requirements: autodesk.com
- EPLAN platform and system requirements: eplan.com
- WineHQ — running Windows applications on Linux and macOS: winehq.org
- QElectroTech — cross-platform open source schematic editor: qelectrotech.org
- FreeCAD — cross-platform open source CAD: freecad.org
Operating system support and licence terms change; verify current requirements with the vendor and in your licence agreement.
Not natively. Autodesk publishes separate system requirements for Windows and macOS, and the Electrical toolset is a Windows product. Mac users typically run it in a Windows virtual machine or on a remote Windows host, subject to the licence terms.
Not as a supported configuration. EPLAN documents Windows as its platform. Linux users sometimes attempt Wine or a virtual machine, but neither is supported and both break on licensing, printing and .NET components.
For plan-based electrical work — walls, rooms, devices, circuits, panel schedules, calculations, PDF and DXF export — yes. The constraint is the browser and the connection, not the chip. Very large drawings and heavy raster underlays are where a thin laptop shows its limits.
No. It requires a connection, and that is a genuine limitation for site work. Download the PDFs and schedules you need before you leave the office; do not plan to design in a basement.
DXF import and export are the reliable path for 2D exchange. DWG is proprietary with many versions and custom objects; expect viewing and conversion rather than editing complex drawings with dynamic blocks. Keep a desktop tool if DWG round-tripping is a hard requirement.
That depends on the vendor, not on the browser. Ask where data is stored, who can access it, whether you can export everything, and what happens if you cancel. A vendor that cannot answer those four questions is not ready for client work.
Design it in the browser
Turn the plan into circuits, a panel schedule, a single-line diagram and a calculated bill of materials. Start free or open the demo.
Open demo See pricing