BricsCAD Printing on Windows vs macOS and Linux
BricsCAD's printing workflow is not identical across operating systems. Windows can use system printers, while Bricsys documents macOS and Linux as PDF-first through Print As PDF.pc3.
Beginner takeaway: Create one CAD sheet standard, but document two output paths: direct system-printer workflow on Windows and PDF-to-OS-printer workflow on macOS/Linux.
What you need to understand first
Ignoring this difference causes confusing support instructions, especially when a Windows user tells a Linux or Mac user to select a physical printer that BricsCAD does not expose directly.
- On macOS/Linux, BricsCAD does not print directly to system printers.
- Print As PDF.pc3 generates the file that is then sent to the physical printer through the OS.
- PAGESETUP remains relevant across platforms.
Related guides: BricsCAD Print As PDF.pc3: What It Is and When to Use It, BricsCAD PC3 Files Explained: Important Differences for AutoCAD Users, and BricsCAD Preview Is Correct but Printed Output Is Wrong.
Step-by-step workflow
Step 1 — Standardize the CAD sheet
Where: DWG/Layout
Do this: Use the same title block, viewport scale and plot-style intent.
Check: Drawing standard is platform-neutral.
Step 2 — Choose platform path
Where: Workstation
Do this: Windows: approved system printer/PC3; macOS/Linux: Print As PDF.pc3.
Check: Output path matches Bricsys behavior.
Step 3 — Apply Page Setup
Where: PAGESETUP
Do this: Use platform-appropriate named setup.
Check: Paper and scale remain consistent.
Step 4 — Create/verify PDF when applicable
Where: BricsCAD PDF output
Do this: Check page size and linework.
Check: The common handoff is correct.
Step 5 — Send to physical printer
Where: OS print system
Do this: Use Actual Size/100% and matching paper.
Check: Hardcopy matches the CAD/PDF standard.
What usually goes wrong
| What you see | Likely layer | First check |
|---|---|---|
| Mac/Linux printer not listed | Expected platform behavior | Use PDF-first workflow. |
| Windows PC3 fails on Mac/Linux | Platform/PC3 difference | Do not port blindly. |
| PDF right, paper wrong | OS printer settings | Check downstream scaling/media. |
| Team gets different results | Different output paths | Standardize verification and named setups. |
Practical example
A mixed Windows/Linux team issues the same A1 drawing. Windows users may plot to the approved system printer; Linux users create an A1 PDF from BricsCAD, verify it, then print that PDF at 100%. The final sheet standard can be identical even though the physical output path differs.
What not to do
- Do not write one Windows-only support procedure for a cross-platform BricsCAD team.
- Do not expect PC3 deployment to solve physical printers on macOS/Linux.
- Do not let the OS print dialog rescale a verified PDF.
Good office standard
Document platform-specific output steps in the CAD manual and use PDF page-size/measurement checks as the common acceptance test.
Quick verification before you move on
- Use one representative drawing or sheet, not a production batch.
- Verify page size, orientation and a known dimension.
- Compare Preview/PDF with the physical output when a printer is involved.
- Save the setting or set only after the result is repeatable.
Official references
Frequently asked questions
Can BricsCAD on macOS/Linux print directly to a system printer?
Bricsys says no; create a PDF with Print As PDF.pc3 and print it through the operating system.
Does that mean Page Setup is useless on Mac/Linux?
No. Page Setup still controls the BricsCAD PDF sheet configuration.
Can Windows users also use PDF-first?
Yes, and it can be useful as a consistent cross-platform verification workflow.
Explore more in BricsCAD Printing & Plotting Guide.