How is a landscape architect’s PDF workflow different from a building architect’s?

The core difference is that landscape practice routinely lives in two PDF worlds at once. One is the technical drawing world — site, grading, planting, and irrigation plans on large-format sheets where scale, line weight, and a searchable plant schedule have to survive exactly. The other is the presentation world — image-heavy boards, renderings, and planting palettes meant to persuade a client or a planning board, where visual richness matters more than measurable precision. A building architect leans heavily toward the first; landscape architects swing between both within a single project, and often a single submittal. The practical upshot is that you need a workflow that can keep crisp vector linework AND handle big rendered images without producing a file nobody can open.

How do I stop my drawings losing scale when I export to PDF?

Two rules. First, export from your CAD or design software at the sheet’s true size and scale — a D-size sheet should produce a D-size PDF page, not a letter-size page with the drawing shrunk to fit. Second, when anyone later views, prints, or re-exports it, make sure "fit to page" or "shrink oversized pages" is turned off, because that silently rescales the geometry and breaks any measurement taken off the sheet. If you need to combine sheets of different sizes into one set, keep each at its native size rather than forcing them all to one page size. Scale fidelity is a property you set at export and then have to protect at every downstream step.

My presentation PDFs with renderings are enormous. How do I shrink them?

Almost all the weight in a presentation set is oversized embedded raster images — renderings, aerials, and photographic references exported at print resolution. Compressing those images to a sensible on-screen resolution typically shrinks the file dramatically while leaving your vector linework, text, and labels perfectly crisp. The key is to compress the images and leave the vector content alone, rather than rasterising the whole page (which would also blur your text and lines). Keep an uncompressed master for printing the boards, and produce a compressed copy for emailing and for posting to a client portal. A 120 MB board set that takes a minute to open undermines the very impression it is meant to create.

Will compressing a grading or contour plan ruin the thin lines?

Not if you compress correctly. The risk people fear comes from tools that rasterise the entire page — turning your vector contours into a flat image that then gets blurred by compression. Sensible PDF compression targets the embedded images and leaves vector linework as vector, so hairline contours, hatching, and dimension lines stay sharp at any zoom. Before issuing a compressed grading plan, zoom in on the densest contour area and confirm the lines are still clean and distinct. If they have softened or merged, the tool rasterised the page — switch to one that compresses images only, or reduce only the embedded reference imagery.

How should I assemble a submittal set so nothing is missing or out of order?

Treat the set like a deliverable, not a folder of files. Merge the individual sheets in the correct sheet order — cover, then plans grouped by discipline (layout, grading, planting, irrigation, details) — into a single PDF, add a cover page and a sheet index, and stamp consistent page numbers so a reviewer can confirm the set is complete at a glance. Before issuing, scroll the whole document once and check the sheet count against your index and that the revision shown matches the one you intend to issue. A missing sheet or a stale revision in a planning submittal costs days; the five minutes of assembly discipline is the cheapest insurance you will buy on the project.

Is it safe to use an online tool for unreleased designs and client work?

Only if the tool works on your own device. Many online PDF tools upload your file to a third-party server, where an unreleased competition entry, an unannounced development, or a client’s site plan may be cached out of your control. Client-side (in-browser) tools do the assembly, compression, and page-numbering locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For anything confidential or pre-public, confirm the tool processes client-side before uploading, or keep the work to offline software. Design work under NDA or competition rules deserves the same caution you would give a contract.

7 min read

PDF for landscape architects — drawings and presentations

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

On a single landscape project I will produce two completely different kinds of PDF in the same week. One is a stack of large-format technical sheets — site layout, grading, planting, irrigation — where a contour line has to stay hairline-crisp and the scale must hold so a contractor can measure straight off the sheet. The other is a presentation set: rendered boards, planting palettes, and aerials meant to win over a client or a planning board, where the images are gorgeous and the file is enormous. Most "PDF tips" articles only address one of those worlds. This guide is written for the reality of swinging between both, often inside one submittal — how to keep scale and linework on the technical sheets, tame the file size on the presentation boards, and assemble a clean issued set.

The documents — and where each one goes wrong

Document	Format	Common gotcha	Fix
Site / layout plan	Large-format sheet (ARCH D/E)	Scale lost when re-exported or fit-to-page	Export at true scale; never let the viewer rescale
Grading & drainage plan	Large-format, dense linework	Thin contour lines vanish on compress	Compress images only, leave vector linework untouched
Planting plan + schedule	Sheet + tabular schedule	Plant schedule text gets rasterised	Keep text as text so the schedule stays searchable
Irrigation plan	Large-format overlay	Layered overlays merge into one heavy image	Flatten only the final issued set, keep a layered master
Presentation board / rendering	High-res image-heavy page	Huge file, slow to open or email	Compress the embedded renders to screen resolution
Submittal / issued set	Multi-sheet bundle	Sheets out of order or missing a revision	Merge in sheet order, add page numbers and a cover

Step by step — a clean PDF workflow for a landscape project

Export technical sheets at true size and scale. Each plan should produce a PDF page at its native sheet size (e.g. ARCH D or E), not a small page with the drawing shrunk to fit. This is what lets a contractor measure off the sheet later.
Keep text as text on plans with schedules. Planting plans and detail sheets carry schedules and labels — export so that text stays selectable rather than rasterised, so the schedule remains searchable and legible at any zoom.
Compress images, never the whole page. For grading and contour plans, use compression that reduces only embedded images and leaves vector linework as vector, so hairlines stay sharp. Avoid any "print to image" or full-page rasterise step.
Make a separate compressed copy of presentation boards.Keep an uncompressed master for printing, and compress the embedded renderings to screen resolution for a copy you can actually email or post to a client portal.
Assemble the issued set in sheet order. Merge the sheets — cover, then layout, grading, planting, irrigation, details — into one PDF, add a cover and sheet index, and stamp consistent page numbers.
Verify before issuing. Scroll the whole set once: check the sheet count against the index, confirm the revision is the one you mean to issue, and zoom into the densest contour area to confirm the linework survived compression.
Share it safely. For confidential or pre-public work, use a tool that processes the file on your own device, and send via an expiring or access-controlled link rather than a public attachment.

The one trade-off to keep in mind

The tension that runs through every landscape PDF is fidelity versus file size, and the honest answer is that you usually want two outputs rather than one compromise. The technical sheets must protect scale and crisp linework even at the cost of size; the presentation set can sacrifice print-grade image resolution for a file that opens instantly on a client’s phone. Trying to make a single PDF serve both ends is where things go wrong — either you ship boards too heavy to open, or you compress a grading plan until the contours blur. Decide up front which copy is for measuring and which is for persuading, and treat them as two deliverables. That single distinction prevents most of the PDF headaches in landscape practice.

FAQ

How is a landscape architect’s PDF workflow different from a building architect’s?: The core difference is that landscape practice routinely lives in two PDF worlds at once. One is the technical drawing world — site, grading, planting, and irrigation plans on large-format sheets where scale, line weight, and a searchable plant schedule have to survive exactly. The other is the presentation world — image-heavy boards, renderings, and planting palettes meant to persuade a client or a planning board, where visual richness matters more than measurable precision. A building architect leans heavily toward the first; landscape architects swing between both within a single project, and often a single submittal. The practical upshot is that you need a workflow that can keep crisp vector linework AND handle big rendered images without producing a file nobody can open.
How do I stop my drawings losing scale when I export to PDF?: Two rules. First, export from your CAD or design software at the sheet’s true size and scale — a D-size sheet should produce a D-size PDF page, not a letter-size page with the drawing shrunk to fit. Second, when anyone later views, prints, or re-exports it, make sure "fit to page" or "shrink oversized pages" is turned off, because that silently rescales the geometry and breaks any measurement taken off the sheet. If you need to combine sheets of different sizes into one set, keep each at its native size rather than forcing them all to one page size. Scale fidelity is a property you set at export and then have to protect at every downstream step.
My presentation PDFs with renderings are enormous. How do I shrink them?: Almost all the weight in a presentation set is oversized embedded raster images — renderings, aerials, and photographic references exported at print resolution. Compressing those images to a sensible on-screen resolution typically shrinks the file dramatically while leaving your vector linework, text, and labels perfectly crisp. The key is to compress the images and leave the vector content alone, rather than rasterising the whole page (which would also blur your text and lines). Keep an uncompressed master for printing the boards, and produce a compressed copy for emailing and for posting to a client portal. A 120 MB board set that takes a minute to open undermines the very impression it is meant to create.
Will compressing a grading or contour plan ruin the thin lines?: Not if you compress correctly. The risk people fear comes from tools that rasterise the entire page — turning your vector contours into a flat image that then gets blurred by compression. Sensible PDF compression targets the embedded images and leaves vector linework as vector, so hairline contours, hatching, and dimension lines stay sharp at any zoom. Before issuing a compressed grading plan, zoom in on the densest contour area and confirm the lines are still clean and distinct. If they have softened or merged, the tool rasterised the page — switch to one that compresses images only, or reduce only the embedded reference imagery.
How should I assemble a submittal set so nothing is missing or out of order?: Treat the set like a deliverable, not a folder of files. Merge the individual sheets in the correct sheet order — cover, then plans grouped by discipline (layout, grading, planting, irrigation, details) — into a single PDF, add a cover page and a sheet index, and stamp consistent page numbers so a reviewer can confirm the set is complete at a glance. Before issuing, scroll the whole document once and check the sheet count against your index and that the revision shown matches the one you intend to issue. A missing sheet or a stale revision in a planning submittal costs days; the five minutes of assembly discipline is the cheapest insurance you will buy on the project.
Is it safe to use an online tool for unreleased designs and client work?: Only if the tool works on your own device. Many online PDF tools upload your file to a third-party server, where an unreleased competition entry, an unannounced development, or a client’s site plan may be cached out of your control. Client-side (in-browser) tools do the assembly, compression, and page-numbering locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For anything confidential or pre-public, confirm the tool processes client-side before uploading, or keep the work to offline software. Design work under NDA or competition rules deserves the same caution you would give a contract.

Citations

Make a client-ready board set in your browser

Shrink an image-heavy presentation set so it opens instantly — ScoutMyTool Compress-PDF reduces the embedded renderings while leaving your linework and labels crisp, and runs client-side so your designs never leave your computer.

Open Compress-PDF tool →