Dia and CAD: DXF Import/Export Guide

Dia Diagram Editor is a free, open-source project by the GNOME community. This site is an independent community resource — we are not affiliated with the GNOME Dia project.

Dia speaks DXF in both directions — it can import .dxf files and export to .dxf (per the official import/export documentation). That makes it a handy free bridge between CAD drawings and presentation-quality diagrams. Here’s what works, what doesn’t, and a practical workflow.

Importing DXF into Dia

1. File → Open, change the file filter to DXF, select your .dwg-converted .dxf file. (Dia reads DXF, not DWG — convert first in your CAD tool or a free converter.)
2. Geometry arrives as editable lines, arcs, and shapes on the canvas. Text usually survives; complex hatches and dimensions may need cleanup.
3. Immediately File → Save As to .dia — do your annotation work in Dia’s native format, not in the imported DXF.

Exporting DXF from Dia

File → Export, choose DXF. What you get is 2D vector geometry your CAD tool can open — useful for sending an annotated layout back to the CAD side.

Fidelity: honest boundaries

Practical workflow: CAD → Dia → document

1. Export the plan from CAD as DXF (2D, cleaned of 3D).
2. Import into Dia; put the CAD geometry on a locked background layer.
3. Annotate on upper layers: callouts, equipment tags, network overlays.
4. Export final as SVG or PDF for the report — or back to DXF if the CAD team needs it.

Dia on Raspberry Pi & Chromebook

Dia Diagram Editor is a free, open-source project by the GNOME community. This site is an independent community resource — we are not affiliated with the GNOME Dia project.

Dia is a native GTK Linux application, which makes it a natural fit for ARM boards and Linux-on-Chromebook setups — no emulation, no hacks. This page covers both.

Raspberry Pi

Install

Raspberry Pi OS is Debian-based, so the standard package just works:

sudo apt update
sudo apt install dia

Launch it from the desktop menu (Accessories/Graphics) or run dia in a terminal.

What to realistically expect

• Small to medium diagrams (class diagrams, flowcharts, home-network maps): perfectly usable, even on a Pi 3.
• Very large diagrams (hundreds of objects, poster-size exports): expect slower redraws — a Pi is not a workstation. Keep diagrams focused and split big ones across pages.
• Display: Dia is an X11/GTK app; it runs fine under Pi OS’s desktop. If you’re on the Lite (headless) image, there’s no GUI to run it in — install the desktop first or use Dia on another machine.

Chromebook

Install via Linux (Crostini)

1. Enable Linux: Settings → Advanced → Developers → Linux development environment → Turn on.
2. In the Terminal app: sudo apt update && sudo apt install dia
3. Dia appears in your launcher under “Linux apps”.

What to expect

Dia runs in the Chromebook’s Linux container as a normal X11 app — diagramming, saving, and exporting all work. File sharing between ChromeOS and Linux files works through the Files app’s “Linux files” section, so getting diagrams in and out is painless. Performance is fine for typical school/office diagrams.

Syncing diagrams

.dia files are tiny (gzipped XML). Sync them with whatever you already use — Google Drive, Nextcloud, git. Just avoid editing the same file on two machines simultaneously; Dia has no merge.

How to Build Dia from Source (Linux)

Dia Diagram Editor is a free, open-source project by the GNOME community. This site is an independent community resource — we are not affiliated with the GNOME Dia project.

Most Linux users should just run sudo apt install dia (see our Linux install guide). Build from source only if you need the absolute latest development code, want to patch something, or your distro doesn’t package Dia. The authoritative instructions live in the BUILDING.md file in GNOME’s Dia repository — always check it first, as dependencies change. What follows is the standard flow.

Prerequisites

You’ll need a compiler toolchain plus Dia’s library dependencies. Install the development packages your distro documents in BUILDING.md — typically this means GTK development files, libxml2, and the Meson/Ninja build tools:

sudo apt install git build-essential meson ninja-build \
  libgtk-3-dev libxml2-dev  # check BUILDING.md for the current list

Build steps

1. Clone the repository

git clone https://github.com/GNOME/dia.git
cd dia

2. Configure with Meson

meson setup builddir

Meson checks for every dependency and reports what’s missing. Fix, re-run.

3. Compile

ninja -C builddir

4. Run without installing (recommended for testing)

./builddir/dia

Or install system-wide with sudo ninja -C builddir install — but running from the build directory keeps your distro’s packaged Dia untouched, which avoids conflicts.

Troubleshooting real build failures

• “Dependency not found”: you skipped a -dev package. The error names it — install and re-run meson setup.
• Python plugin fails to build: this is the most-reported issue (seen on distro forums) — the Python bindings need matching Python dev headers. If you don’t need scripting, you can often disable that component at configure time; check meson configure options.
• Old Meson version: distro Meson packages lag; pip install --user meson gets you a current one.
• Stale build directory: after pulling new code, wipe builddir and re-run setup rather than fighting cached state.

This is an independent community resource about Dia. We are not affiliated with the GNOME Dia project. PyDia documentation is sparse — the examples below are minimal, tested patterns; adapt property names to your Dia build.

Automate Dia with Python Scripting

Dia embeds a Python interpreter (“PyDia”). That means repetitive diagram chores — exporting every layer, renaming dozens of objects, generating repetitive drawings — can be scripted instead of clicked. This page gives you the smallest useful starting points.

Opening the Python Console

In Dia: Tools > Python Console (menu location may vary slightly by version — look under Tools or Plugins). A console window opens with the dia module pre-imported, bound to the currently active diagram.

Example 1: List Layers and Objects

import dia
d = dia.active_display().diagram
for layer in d.layers:
    print("Layer:", layer.name, "-", len(layer.objects), "objects")

Run this with a diagram open. If it prints your layers, scripting works in your build.

Example 2: Batch-Export Every Layer as PNG

import dia
d = dia.active_display().diagram
for layer in d.layers:
    # hide all layers, then show only this one
    for l in d.layers:
        l.visible = (l is layer)
    d.export("/tmp/layer-%s.png" % layer.name)
# restore visibility
for l in d.layers:
    l.visible = True
d.flush()

This is the classic use case: one diagram with per-customer/per-version layers, exported to separate files automatically.

Example 3: Rename Objects in Bulk

import dia
d = dia.active_display().diagram
n = 0
for layer in d.layers:
    for obj in layer.objects:
        props = obj.properties
        if "name" in props:
            props["name"].value = "node-%02d" % n
            n += 1
d.flush()

Running Scripts Non-Interactively

Dia can run a script file at startup, which pairs with command-line export for fully automated pipelines: generate or modify diagrams in Python, then export without touching the GUI.

Where to Go Next

• The PyDia API is documented mainly in the Dia source tree and scattered wiki pages — search for “PyDia” plus your specific need.
• For one-off automation, the console is enough. For anything bigger, consider whether a code-first tool like PlantUML fits the workflow better — honest advice, not a sales pitch.

Frequently Asked Questions

This is an independent community resource about Dia. We are not affiliated with the GNOME Dia project. Command examples below were verified against Dia’s documented CLI behavior; flags may vary slightly by build.

Dia Command Line: Batch Export Diagrams

Dia is a GUI app — but it ships with a genuinely useful command-line mode. dia -e converts diagrams without opening a window, which means you can batch-export hundreds of .dia files, or wire diagram generation into documentation builds and CI pipelines. This guide covers the practical patterns.

The Basics

dia -e output.png input.dia        # export one diagram to PNG
dia -e output.svg input.dia        # vector SVG for documents
dia -e output.pdf input.dia        # PDF for print/runbooks

The export format is inferred from the output extension. Common choices: png, svg, pdf, eps. On Windows, run this from the Dia installation’s bin directory or add it to your PATH.

Batch: Convert a Whole Folder

# Linux/macOS: export every .dia in docs/ to PNG
for f in docs/*.dia; do
  dia -e "${f%.dia}.png" "$f"
done

# Windows PowerShell equivalent
Get-ChildItem docs\*.dia | ForEach-Object {
  & dia.exe -e ($_.FullName -replace '\.dia$','.png') $_.FullName
}

Multi-Page Diagrams

If a .dia file has multiple pages, Dia exports each page — output filenames get a page suffix automatically. Verify the naming with one test file before batching hundreds.

Putting It in a Build (Makefile Example)

DIAGRAMS := $(wildcard diagrams/*.dia)
IMAGES   := $(DIAGRAMS:.dia=.png)

docs: $(IMAGES)

%.png: %.dia
	dia -e $@ $<

clean:
	rm -f $(IMAGES)

Now make docs regenerates every diagram image whenever sources change — diagrams stop rotting in your documentation.

CI Pipeline Notes

• Install Dia in the CI image (apt install dia on Debian/Ubuntu runners) plus xvfb for headless export.
• Pin the Dia version in your pipeline — rendering can shift subtly between builds.
• Commit both .dia sources and generated images, or generate images as a build artifact.

For programmatic diagram generation (not just export), see automating Dia with Python.

Frequently Asked Questions

This is an independent community resource about Dia. We are not affiliated with the GNOME Dia project. The timeline below is compiled from public sources (GNOME wiki, dia-installer.de, Wikipedia).

Is Dia Still Maintained in 2026?

The Honest Timeline

What “Maintenance Mode” Means for You

• It will not suddenly stop working. Dia is a local desktop app with no servers to shut down and no license checks to expire. Your diagrams are safe.
• Don’t expect new features. No dark mode overhaul, no real-time collaboration, no .vsdx import is coming. Judge Dia on what it does today.
• Security risk is minimal. It is an offline drawing tool that never touches the network. The attack surface is about as small as software gets.
• Community resources persist: the shape repository, installer downloads and documentation remain online.

Should You Still Use Dia in 2026?

Yes, if: you need a free, offline, lightweight diagram tool for UML, flowcharts, network maps or schematics — the things Dia has always done well. Look elsewhere if: you need real-time collaboration, cloud sync, or modern UI polish — see our free Visio alternatives roundup for honest options. Neither answer is a tragedy; it is just matching the tool to the job.

Frequently Asked Questions

Microsoft Visio is the industry standard for professional diagramming — and it is also paid, subscription-based, and historically Windows-centric. The good news: for most real-world diagramming work (UML diagrams, flowcharts, network maps, org charts, floor plans), you do not need it.

Below are 9 honest Visio alternatives for 2026, starting with Dia itself. Every tool gets the same treatment: who it is best for, genuine pros and cons, and an honest pricing note. No sponsored rankings, no invented review scores — just what each tool actually does well and where it falls short.

How We Picked These 9

Three rules decided the list. First, no free trials masquerading as free tools — every entry here is usable long-term without paying, whether that means open source, freeware, or a genuinely usable freemium tier. Second, it must actually do diagramming — general design tools like Canva are great at posters, but their connector routing and shape libraries are not built for UML or network diagrams, so they did not make the cut. Third, no dead software — every tool below is maintained and downloadable today. That is also why the list mixes four truly-free tools with five freemium/paid ones: the honest answer to “Visio alternative” depends on whether you need free-as-in-beer or collaboration-as-a-service.

Quick Comparison Table

The 9 Best Free Visio Alternatives in 2026

How to Choose the Right One

Match the tool to your situation, not to a “best overall” crown:

• You want free forever and offline → Dia. Nothing else on this list is both 100% free and fully offline. Download it here.
• You need a diagram in the next five minutes, no install → diagrams.net in the browser.
• You have a giant, tangled graph → yEd and its automatic layout.
• You already run LibreOffice → Draw covers occasional diagrams with zero new software.
• Your team edits diagrams together, live → Lucidchart or Miro (Miro if it is mostly brainstorming).
• You want templates plus a human support team → EdrawMax.
• Your workplace runs on Microsoft 365 → Visio is the path of least resistance.

One honest rule of thumb: free tools (Dia, diagrams.net, yEd, LibreOffice Draw) are single-user and community-supported. You pay for collaboration, polish, templates, and someone to call when it breaks — not for the ability to draw boxes and arrows, which has been free for decades.

A final filter before you decide: check the file formats you actually receive. If your workflow is 90% .vsdx files from colleagues, prioritize import fidelity (Visio, Lucidchart, EdrawMax) over ideology. If you mostly create diagrams and export them as PDF, PNG, or SVG for reports and documentation, any of the four free tools will serve you for years — SVG export from Dia and diagrams.net, in particular, stays crisp at any zoom level, which matters when your diagram ends up projected in a lecture hall.

What Didn’t Make the List (and Why)

A few names you might expect, and why they are absent. Canva and Visme are excellent design tools, but their diagramming is template-deep: try routing fifty connectors in a network topology and you will feel the difference. OmniGraffle is superb on Mac but Mac-only and paid, which fails both the cross-platform and free tests. Old freeware like Diagram Designer still floats around download sites, but it is unmaintained — running unmaintained binaries from random mirrors in 2026 is a security posture we will not recommend. And “free trial” versions of paid tools are marketing, not alternatives; they expire.

Frequently Asked Questions

Dia Portable · Updated October 2026

Dia Portable is the no-install edition of the Dia diagram editor for Windows: extract a ZIP file to a USB stick (or any folder) and run it — no installer, no admin rights, no registry changes. Your settings and recent files travel with the stick, so your diagramming setup is identical on every PC you plug into.

Download Dia Portable

Download Dia Portable (.zip)
Based on official upstream 0.97.2 · extract & run · Windows 11 / 10 / 8 / 7 · 100% free, GPL licensed

How to use it (60 seconds)

1. Extract the downloaded ZIP to a folder — e.g. E:\DiaPortable on your USB stick, or C:\Tools\DiaPortable on a local drive. Any unzip tool works; Windows’ built-in “Extract All” is fine.
2. Run DiaPortable.exe (or dia.exe inside the folder, depending on the package layout).
3. That’s it. Dia opens with the full shape libraries (UML, flowchart, network, electrical). Your preferences, custom shapes, and recent-file list are saved inside the portable folder — move the folder and everything moves with it.

High-DPI / blurry text fix

The portable build is the same 0.97.2 codebase, so the same high-DPI workaround applies:

1. Right-click DiaPortable.exe → Properties → Compatibility → Change high DPI settings.
2. Check Override high DPI scaling behavior, set Scaling performed by to System (or System (Enhanced) on Windows 11).
3. Restart Dia. The setting is stored by Windows per-executable path, so it sticks as long as the USB drive letter doesn’t change — if Windows assigns a different drive letter, reapply once.

Keeping your portable setup in sync

• Back up the whole folder. Your .dia diagrams, preferences, and any custom shapes in the portable profile live inside the extracted folder — copying the folder is a complete backup.
• Custom shapes go in the portable profile’s shapes directory (mirrors ~/.dia/shapes on a normal install); they load on next launch.
• Don’t run it from a network share if you can avoid it — GTK+ 2 apps can be sluggish over SMB. Copy to a local disk or USB 3 stick instead.
• Eject safely. Close Dia before unplugging the stick so your last settings are flushed to disk.

When to choose portable vs. installed

Choose portable if you work on locked-down office or lab PCs, hop between computers, or want a zero-footprint toolkit. Choose the standard installer if Dia lives on your own PC permanently — installed mode gives you Start-menu integration and file-type association for .dia files (double-click to open).

Both editions are the same free GPL software and open each other’s files without conversion.

Plain ZIP vs. PortableApps format

You may encounter two kinds of “portable” Dia online. Here’s the difference, honestly stated:

• Plain ZIP portable (what we link above): the official upstream binaries repackaged to run from any folder, with settings kept in a self-contained profile inside the folder. Simple and transparent.
• PortableApps-format packages: community repackagings that add a PortableApps launcher. They work the same way but add a wrapper layer — useful only if you already manage a PortableApps menu.

Both are the same GPL software underneath. We link the plain ZIP because it has the fewest moving parts.

Where portable shines: real scenarios

• Office PC without admin rights: keep Dia on a USB stick and diagram during lunch — no IT ticket required.
• University labs: lab machines wipe themselves on reboot; your USB stick doesn’t.
• Client sites: sketch network diagrams on the client’s machine without installing anything on it.
• Clean-room testing: evaluate Dia without touching your system’s registry or package database.

Syncing with an installed copy

Portable and installed Dia share the .dia file format, so moving diagrams between them is just file copying. If you use both regularly, keep your diagrams in a synced folder (Nextcloud, Syncthing, or plain USB) and open them from whichever edition is at hand. Settings don’t sync between the two — portable keeps its own profile by design — so set your default font and preferences once in each.

Security and antivirus notes

The portable launcher is not code-signed, so you may see one or both of these:

• Windows SmartScreen (“unrecognized app” / “unknown publisher”) — click More info → Run anyway. This is expected for unsigned open-source builds.
• Antivirus false positives — decade-old unsigned executables occasionally trip heuristic scanners. If your AV quarantines the file, restore it and submit it as a false positive to your AV vendor; the package is built from the unmodified upstream 0.97.2 release.

General rule for any portable software: download only from sources you trust, and prefer packages that document exactly which upstream release they were built from — as this page does.

Windows on ARM (Snapdragon) note

Dia Portable is an x86/x64 application. On Windows-on-ARM devices (e.g. Snapdragon laptops) it runs through Microsoft’s Prism/x86 emulation layer. Basic diagramming generally works, but this combination is not officially tested by the Dia project — on ARM hardware, the Linux build (native ARM via your distro’s repository) is the more predictable option.

Related: Dia for Windows · Dia for Mac · Dia for Linux · main download page · FAQ.

Dia on Linux · Updated October 2026

Linux is Dia’s home turf — it’s a GNOME project, after all. Installing Dia on Linux is the easiest of all platforms: most distributions ship it in their official repositories, and the repository builds are typically newer than the Windows release. This guide covers Ubuntu/Debian, Fedora, Arch, and building from source.

Install from your package manager (recommended)

Using your distro’s repository is the best option: you get dependency handling, updates, and a build compiled for your system. Open a terminal and run the command for your distribution:

Ubuntu / Debian / Linux Mint / Pop!_OS

sudo apt update
sudo apt install dia

Fedora / RHEL / CentOS Stream

sudo dnf install dia

Arch Linux / Manjaro

sudo pacman -S dia

openSUSE

sudo zypper install dia

After installation, launch Dia from your application menu or by typing dia in the terminal.

Version notes: Linux builds are newer than Windows

The 0.97.3 release (2014) fixed bugs and updated translations over 0.97.2 but was never officially packaged for Windows or Mac — which is why the Windows guide still points at 0.97.2. On Linux you transparently get the newer code. Feature-wise the differences are minor for everyday flowchart, UML, network, and ER diagramming.

Install from source tarball

If your distribution doesn’t package Dia, or you want the exact upstream release, grab the source tarball and build it. You’ll need a compiler and the GTK+ 2 / GNOME development libraries — check your distro’s documentation for the exact -dev package names.

Download Dia Source (.tar.xz)
Official upstream source · free · GPL licensed

Typical build sequence once dependencies are in place:

tar -xf dia-0.97.2.tar.xz
cd dia-0.97.2
./configure
make
sudo make install

Extra shape libraries on Linux

Dia’s power comes from its shape sheets (UML, network, flowchart, electrical, and more). On Linux:

• The repository package already includes the standard sheets — enable them via File > Sheets and Objects.
• Diashapes is a community tool for installing additional shape collections (e.g. Cisco, AWS-style icons) from the Dia Shape Repository.
• Custom .shape files go in ~/.dia/shapes/; restart Dia to pick them up.

Wayland notes

Dia is a GTK+ 2 / X11 application. On Wayland sessions it runs through XWayland, which most distributions enable by default. If Dia refuses to start on a pure-Wayland setup, try launching it from a terminal with GDK_BACKEND=x11 dia, or log into an “Xorg” session from your display manager.

Command-line export (batch conversion)

Dia can export diagrams without opening the GUI — handy for scripts and Makefiles:

# Export a .dia file to PNG (1024 px wide)
dia -e output.png input.dia

# Export to SVG
dia -e output.svg input.dia

# See all options
dia --help

This makes Dia a surprisingly good fit for documentation pipelines: keep diagrams as .dia sources in version control and regenerate the exported images on every build.

Dia on Raspberry Pi and ARM

Because distributions compile Dia from source, it works on ARM Linux too — including Raspberry Pi OS:

sudo apt install dia

Performance on a Pi 4/5 is perfectly usable for typical flowcharts and UML diagrams. The same applies to ARM servers and Asahi Linux on Apple Silicon Macs (where the Linux build is a more predictable option than the untested Mac/Intel build under Rosetta).

Desktop integration

The repository package registers Dia with your desktop environment automatically: you’ll find it in the application menu (usually under Graphics or Office), and .dia files get a proper icon and double-click-to-open association. If you built from source with make install, menu integration may be missing — launching via terminal (dia) always works.

Troubleshooting common Linux issues

Dia is installed but not in the application menu

This happens with make install from source. Either launch it from the terminal with dia, or copy the desktop entry manually: sudo cp data/dia.desktop /usr/share/applications/ (path varies by build).

Interface is in the wrong language

Dia follows your system locale. To force English for one session: LANGUAGE=en dia. To check available translations, look at the component selection — the repository package usually splits translations into a dia-common or language-pack package; make sure it’s installed.

Shapes or icons are missing

A minimal install can skip the shape libraries. On Debian/Ubuntu, ensure the full dia package (not just a split-out binary) is installed. Then open File > Sheets and Objects inside Dia and tick the sheets you need.

Fonts look different than on Windows

Dia uses whatever fonts your system provides. For diagrams shared with Windows users, stick to widely available fonts (DejaVu Sans ships with most distros and has a Windows counterpart in metric-compatible form). Export to SVG embeds text as text — the viewer’s fonts apply — while PNG bakes your local fonts into pixels.

Useful keyboard shortcuts

Other platforms: Dia for Windows · Dia for Mac · main download page · FAQ.

Dia on macOS · Updated October 2026

Yes, Dia runs on the Mac — but with important caveats every Mac user should know before downloading. Dia’s Mac build is an older Intel package that requires XQuartz (Apple’s X11 windowing system), and Apple Silicon support has never been officially tested. This guide gives you the honest picture: what works, what doesn’t, and the exact installation order that avoids the classic “Dia won’t start” problem.

What you need before installing

Step 1 — Install XQuartz (do this first)

Dia on macOS is an X11 application, which means it draws its windows through the X Window System instead of native Cocoa. Modern macOS no longer ships X11, so you must install XQuartz first. Installing Dia before XQuartz is the #1 reason for “nothing happens when I double-click Dia.”

Download XQuartz
Official XQuartz release · free · required for Dia on Mac

1. Open the XQuartz .dmg and run the installer package.
2. Log out and log back in (or restart your Mac). This step is mandatory — XQuartz only becomes available to other apps after a fresh login.
3. After logging back in, open XQuartz once from Applications > Utilities to confirm it launches.

Step 2 — Download and install Dia for Mac

Download Dia 0.97.2 for Mac
Official upstream build · .dmg · Intel 64-bit · 100% free, GPL licensed

1. Open the downloaded .dmg and drag Dia into your Applications folder.
2. The first launch may be blocked by Gatekeeper (“Dia can’t be opened because it is from an unidentified developer”). Right-click (or Control-click) Dia in Applications, choose Open, then click Open in the dialog. You only need to do this once.
3. Dia should now start inside an XQuartz window. First launch is slow — give it up to a minute while it loads shape libraries.

Apple Silicon (M1/M2/M3/M4) notes

To be completely transparent: the Dia project has never released or tested a native Apple Silicon build. What some users do:

• Install Rosetta 2 (macOS prompts you automatically when needed).
• Install the Intel build of XQuartz, then the Intel Dia .dmg above.
• Launch Dia and see. Reports are mixed: basic diagramming often works, but font rendering and stability issues are more common than on Intel Macs.

We will not claim “full M-series support” because we cannot verify it. If Dia proves too fragile on your Apple Silicon Mac, the Linux build (in a VM) or the Windows build are more predictable ways to run the same software.

Troubleshooting

Dia bounces in the Dock and quits

Almost always means XQuartz isn’t properly installed or you skipped the log-out/log-in step. Reinstall XQuartz, restart the Mac, then try again.

Fonts look broken or tiny

X11 font handling on modern macOS is rough. Inside Dia, set the default font to a basic X11-available font. If text is microscopic on a Retina display, there is no perfect fix in the 0.97.2 build — exporting to SVG and viewing in a browser gives the truest preview of your diagram.

Keyboard shortcuts feel wrong

X11 apps use Ctrl-based shortcuts. In Dia on Mac, Ctrl+S saves (not Cmd+S). You can remap some behavior in XQuartz preferences, but most users just adapt.

Advanced alternative: MacPorts

The Dia .dmg above was itself built using MacPorts. If you already use MacPorts, you can install Dia from source ports instead:

sudo port install dia

This compiles Dia (and its dependencies) for your system. You still need XQuartz, and on Apple Silicon the same “not officially tested” caveat applies — MacPorts builds run through the same X11 stack. Only take this route if you’re comfortable with MacPorts; for everyone else, the DMG is simpler.

Copy, paste, and keyboard habits

A few X11 realities worth knowing up front so they don’t surprise you:

• Shortcuts use Ctrl, not Cmd. Ctrl+S saves, Ctrl+Z undoes, Ctrl+C/Ctrl+V copy and paste inside Dia.
• Clipboard sharing with Mac apps is unreliable. Copying a diagram out of Dia as an image and pasting into Keynote usually doesn’t work; export to PNG or SVG first, then import the file.
• Right-click works (or Control-click) for context menus on objects.
• File dialogs are X11-style, not native Mac sheets — navigation feels dated but is fully functional.

Uninstalling Dia and XQuartz

Drag Dia from Applications to the Trash. If you installed XQuartz only for Dia, you can remove it the same way (Applications > Utilities > XQuartz) — but leave it in place if any other X11 app might need it. Your .dia files and the ~/.dia/ settings folder remain until you delete them manually.

Other platforms: Dia for Windows · Dia for Linux · main download page.