cadblockdwg
Resources

DWG vs DXF for paving patterns: which format to download

Paving patterns are hatch-heavy geometry where the format can matter. Here is when DWG vs DXF is the better paving download, and how to keep the pattern clean.

Saumyajit MaityUpdated 6 February 20265 min read

dwg-vs-dxf-paving-patterns-which-format
Illustration for “DWG vs DXF for paving patterns: which format to download”

Default to DWG, but paving has a wrinkle

For most paving downloads the usual advice holds: take the DWG. A paving block, a setts pattern or a stretcher-bond layout is vector geometry that opens cleanly as DWG in every mainstream CAD tool, and our Paving category serves it as free DWG with no signup and free commercial use. So the default is unchanged.

The wrinkle is that paving relies on hatches and repeating patterns more than most block families, and hatches are one of the few things that can behave differently across formats and software. A custom hatch pattern defined in a DWG may not survive intact when read by a program that does not share that pattern definition. That makes the DWG-versus-DXF question slightly more interesting for paving than for a plain object like a chair — worth understanding before you commit a large paved area to one format.

Why hatches complicate the format choice

Paving is often drawn as a boundary filled with a hatch — running bond, herringbone, basketweave, stack bond — and the appearance depends on the pattern definition, scale and origin. Within the AutoCAD ecosystem, a DWG carries all of that faithfully. Across software boundaries, two things can go wrong: a program may not recognise an associative or custom hatch, and a DXF round-trip can occasionally simplify a hatch into individual lines or lose its associativity.

For exchange, that can actually be a feature. If you explode or convert a paving hatch into real linework before handing it off, the pattern becomes plain geometry that any program reads identically — at the cost of a heavier file and losing the ability to edit it as a hatch. So the paving format decision is partly about whether you want to keep the pattern editable (favour DWG, native) or guarantee it survives a software jump (favour exploded geometry, often via DXF).

When to download paving as DXF

Download or convert to DXF when the paving has to leave AutoCAD — into GIS to sit on survey data, into a terrain or site tool, or to a contractor or fabricator on different software. If a setting-out pattern is going to a CNC or waterjet to cut physical pavers or a template, DXF is the fabrication-friendly format, and you will usually want the pattern as explicit closed outlines rather than a live hatch.

For a paving layout that stays inside your AutoCAD or DWG-native drawing — where you want to keep tweaking the bond pattern, scale and joint lines — the DWG is better, because it preserves the hatch as an editable object. So match the download to the destination: editable pattern in a DWG-native drawing, or portable explicit geometry via DXF when the paving crosses into other software or fabrication.

Keeping a paving pattern clean on insertion

Download the paving block or pattern, INSERT it, and set out the pattern from a deliberate origin — a building corner or a key edge — so joints align with the architecture rather than starting at a random point. Check the scale carefully: a paving unit is a real size (a common block paver is around 200 by 100mm), so dimension a single unit to confirm the pattern is at the correct scale before you fill a whole area. A mis-scaled paving hatch makes the whole layout misleading.

Keep paving on its own layer so you can control its lineweight and dim it behind site furniture or planting, and so a busy pattern does not clutter other sheets. If you are handing the paving off and the receiving software might not honour the hatch, convert it to linework first and verify it looks right. After importing unfamiliar paving, run AUDIT and PURGE to clear any orphaned pattern definitions the block dragged in.

Hatch pattern vs individual block — two ways to pave

There are really two ways a paved area arrives, and they behave differently across formats. One is a true hatch: a boundary filled with a pattern, light in the file and easy to re-scale, but dependent on the receiving software recognising the pattern definition. The other is an array of individual paver blocks — a single paving unit copied or arrayed across the area — which is heavier but completely explicit, so it reads identically everywhere, including after a DXF round-trip or in fabrication.

For a setting-out drawing or a fabrication file, the explicit array (or an exploded hatch) is the safer choice because there is no pattern definition to lose. For a presentation or a large area you are still adjusting, the hatch is lighter and quicker to edit. Knowing which you are working with tells you what to expect from the format: a hatch may need converting to survive a software jump, whereas an array of paver blocks already travels as plain geometry and will not surprise you on the other side.

The paving format rule

Keep paving as a DWG while you are designing and editing the pattern in AutoCAD or a DWG-native tool — it preserves the hatch as a live, adjustable object. Move to DXF, usually with the pattern exploded to explicit outlines, when the paving has to cross into GIS, terrain tools, other software, or fabrication, where a live hatch may not survive but plain geometry always will.

The geometry of the pavers is identical either way; the real variable is whether the repeating pattern stays editable or becomes fixed linework. Decide that based on where the paving is going, set it out from a deliberate origin at the correct unit scale, and keep it on its own layer. Handle the hatch deliberately and a downloaded paving pattern will read cleanly whether it stays on screen or goes to a cutting machine.

Tagsdwgdxfpavinghatchlandscapefile formats

Questions

Frequently asked

DWG or DXF for paving patterns?+

DWG while you design and edit the pattern in AutoCAD, because it keeps the hatch editable. Use DXF — usually with the pattern exploded to outlines — when paving crosses into GIS, other software or fabrication.

Why can a paving hatch look wrong after exchange?+

Custom or associative hatch patterns may not be recognised by other software, and a DXF round-trip can simplify or lose the hatch. Exploding the pattern into real linework before handoff makes it read identically everywhere.

How do I keep paving at the right scale?+

Dimension a single paving unit (a common block paver is about 200x100mm) to confirm the pattern scale before filling an area, and set the pattern out from a deliberate origin like a building corner.

Free downloads from this article

Paving CAD blocksTrees & Plants CAD blocksHow to Insert a Tree CAD Block in AutoCADFree Landscape & Tree DWG Pack — Plan & ElevationFree Landscape CAD Block Pack — DWG & DXF

Free CAD block library

Download the blocks from this article — free, no signup

Browse CAD blocks

Keep reading

Related articles

← Back to all articles