3D handoff
Import a DeckDraft model into SketchUp
Start in DeckDraft: open the job, choose 3D, then select Download > SketchUp ZIP. Import that package at full scale in SketchUp Desktop or SketchUp for Web.
Use this guide to
- Find and download the SketchUp ZIP from the DeckDraft 3D view
- Choose the correct Desktop or Web import path without losing textures
- Verify scale, organization, materials, and model scope after import
- Optionally convert repeated groups into reusable SketchUp components
Start here
- In DeckDraft
- Open job > 3D > Download > SketchUp ZIP
- Model file
- deckdraft-model.dae (COLLADA 1.4.1)
- Declared unit
- Foot; imported at full model scale
- Best use
- Visual editing, context, rendering, and presentation
Download the model from DeckDraft
The export starts inside the DeckDraft job—not in SketchUp. Open the job you want to share, switch to the 3D view, and use the Download menu in the workspace control bar.
- 1Open the job in DeckDraftOpen the saved customer job and confirm this is the revision you intend to send.
- 2Choose 3DSelect 3D in the workspace view row and wait for the assembled model to appear.
- 3Click DownloadIn the 3D workspace control bar, open Download, then choose SketchUp ZIP. On a compact layout, choose Export SketchUp ZIP in the 3D controls.
- 4Keep the downloaded ZIP togetherYour browser saves a file beginning deckdraft-sketchup-. Keep that original ZIP intact until you choose the Desktop or Web instructions below.
Choose the SketchUp import path
DeckDraft exports a COLLADA handoff package rather than a native .skp file. SketchUp reads the DAE geometry and its referenced texture images, after which you save the imported result as a normal SketchUp model.
Use the standard import for most handoffs. The optional component helper is useful only when the recipient plans to edit many repeated boards, posts, pickets, or similar parts in SketchUp.
| Destination | What to give SketchUp | Use this path when |
|---|---|---|
| SketchUp Desktop — standard | Extract the ZIP, then import deckdraft-model.dae | You want the most predictable import, texture troubleshooting, and a normal .skp save |
| SketchUp for Web | Keep the DeckDraft package zipped and upload the ZIP through Import | You are working in the browser and the current SketchUp plan exposes DAE/ZIP import |
| SketchUp Desktop — components | Extract the ZIP, then run deckdraft-componentize.rb once from Ruby Console | You want equal repeated parts to share native SketchUp component definitions |
Keep the package contents together
The ZIP is a small folder-based model package. Desktop users should extract the entire archive to one folder; moving only the DAE commonly causes missing materials.
| Package item | Purpose | Handling rule |
|---|---|---|
| deckdraft-model.dae | COLLADA 1.4.1 geometry with named assembly groups, reusable component nodes, material references, and declared foot units | Import this file in SketchUp Desktop; do not rename or move it away from textures before import |
| textures/ | Image files referenced by the DAE for supported decking, roof, screen, and other modeled materials | Keep the folder beside deckdraft-model.dae with its name and internal files unchanged |
| README-SketchUp.txt | Portable import, verification, component, and troubleshooting instructions | Send it with the package when another person will perform the import |
| deckdraft-componentize.rb | Optional helper that turns repeated imported leaf groups into shared SketchUp component definitions | Desktop only; run once from Ruby Console after reviewing the script and this guide |
Import into SketchUp Desktop
- 1Extract the complete ZIPCreate a job-specific folder and extract every file. Confirm deckdraft-model.dae and the textures folder are side by side.
- 2Start with an empty SketchUp modelA clean file makes scale, origin, hierarchy, and accidental duplicates easier to verify. You can move the imported deck into a larger site model after checking it.
- 3Choose File > ImportSet the file type to COLLADA File (*.dae), browse to the extracted folder, and select deckdraft-model.dae.
- 4Review DAE import optionsLeave Validate COLLADA File enabled. For a normal presentation import, leave Merge Coplanar Faces enabled; retry with it disabled only when you specifically need the original triangulated faces or are diagnosing a surface issue.
- 5Import and frame the modelChoose Open on Windows or Import on macOS. When the model is not visible immediately, use Zoom Extents before assuming the import failed.
- 6Verify, then save as SKPMeasure one known deck width or projection, inspect the named category groups, repeated component instances, and materials, then use Save As to create the working .skp file. Keep the extracted source folder until verification is complete.
- Use Outliner to find high-level groups such as Deck boards, Support beams, Support posts, Rails, House walls, Roof surfaces, and References; repeated equal parts should appear as component instances where the import path preserves COLLADA node definitions.
- Keep the imported hierarchy grouped while orienting the model; exploding the whole project turns separated component geometry back into connected raw faces.
- Move or rotate the top-level imported groups only after the known-dimension check passes.
Import into SketchUp for Web
SketchUp for Web uses a ZIP package for DAE models with external textures because the browser cannot freely read a sibling folder on your device. In this path, keep the DeckDraft download zipped.
- 1Leave the DeckDraft ZIP intactDo not upload deckdraft-model.dae by itself. The archive carries the texture folder and paths SketchUp needs.
- 2Open ImportFrom the SketchUp for Web main menu, choose Import, then My Device.
- 3Choose the DeckDraft ZIPBrowse to the downloaded deckdraft-sketchup-.zip file and complete the import. If the ZIP or DAE choice is unavailable, the current SketchUp plan may not include that import capability.
- 4Frame and verify the modelUse Zoom Extents if necessary, measure a known deck dimension, inspect materials and hierarchy, then save the working model to the intended Trimble Connect project.
Verify the handoff before editing
A successful import is more than seeing a deck on screen. Check scale and content before adding site context, rendering assets, dimensions, or customer-facing scenes.
| Check | Expected result | If it does not match |
|---|---|---|
| Scale | A known bay width or projection measures the same as DeckDraft; the DAE declares feet at 0.3048 meters per unit | Undo or close without saving and reimport as COLLADA; do not eyeball-rescale the model |
| Organization | Outliner exposes named project categories and nested repeated component instances instead of one collection of connected faces | Confirm you imported deckdraft-model.dae from the DeckDraft package and did not explode the imported hierarchy; on Desktop, use the fallback helper only if repeated leaves arrived as ordinary groups |
| Materials | Supported colors and texture images appear on the intended surfaces | Re-extract the original ZIP and confirm textures remains beside the DAE; then import again |
| Transparency | Screens and other transparent surfaces remain visible with partial opacity | Compare another SketchUp face style/render mode before changing material opacity |
| Scope | The 3D deck, house context, framing, supports, finishes, rails, stairs, and applicable cover geometry are present | Return to DeckDraft, verify the modeled job and 3D assembly, then create a new export |
| Documents | Plan dimensions, callouts, schedules, takeoff notes, and PDF sheets are not part of the SketchUp model | Share the DeckDraft plan set separately when the recipient needs construction or permit information |
Handoff acceptance check
- Record the DeckDraft job revision and export date
- Measure at least one width and one projection in SketchUp
- Inspect stairs, rails, house walls, supports, and roof geometry
- Confirm key finish colors and texture placement
- Check Outliner organization before exploding or regrouping
- Save the verified working file as .skp
- Share the plan set separately when dimensions or construction information are required
- Re-export instead of silently editing an outdated DeckDraft model
Optional fallback: convert repeated groups into components
The DAE already defines reusable component nodes for equal repeated parts. Use the included helper only when a SketchUp Desktop version or import path turns those leaf nodes into ordinary groups; skip it when Outliner already shows component icons.
As a fallback, the helper matches repeated leaf groups by category, exact rounded dimensions, and material names. Equal boards, posts, pickets, joists, and similar repeated parts can then share one component definition while retaining their individual placements.
- 1Work in a fresh or just-imported fileExtract the package and import the DAE normally first. If repeated leaves are ordinary groups, run the helper before manually exploding or regrouping the model; if they are already components, do not run it.
- 2Open Ruby ConsoleIn SketchUp Desktop, choose Window > Ruby Console.
- 3Load the extracted helperEnter a load command using the actual extracted path and forward slashes, for example: load "C:/Users/Name/Downloads/deckdraft-sketchup-job/deckdraft-componentize.rb"
- 4Read the completion messageSketchUp reports how many groups were converted, how many component definitions were created, and how many repeated instances were reused.
- 5Inspect and saveReview Outliner and Components, measure the model again, then save the working .skp file under a new revision-aware name.
Troubleshoot common import problems
| Symptom | Likely cause | Corrective action |
|---|---|---|
| Nothing appears after import | The model is outside the current camera frame | Use Zoom Extents, then check Outliner before importing again |
| Model is white or key textures are missing | The DAE was moved away from textures, uploaded alone, or opened inside the ZIP | Re-extract the original package; keep textures beside the DAE on Desktop, or upload the intact ZIP on Web |
| Model appears twice | The DAE or component helper was run more than once | Undo immediately or close without saving and repeat the workflow once in a clean file |
| Model is extremely small or large | The file was imported through the wrong format/workflow or later rescaled | Reimport the DAE as COLLADA, validate a known dimension, and preserve the declared foot unit |
| Too many diagonal face edges are visible | Triangulated COLLADA faces were preserved | Reimport with Merge Coplanar Faces enabled, or hide/soften edges only after the dimension check |
| A repeated part is difficult to edit globally | The import path flattened reusable COLLADA nodes, or the imported hierarchy was exploded | Reimport without exploding the model; if Desktop still produces ordinary leaf groups, use the optional component helper once before manual regrouping |
| Ruby Console reports a path or file error | The ZIP is not fully extracted or the load path is incorrect | Confirm the .rb and .dae are in the extracted folder and use the exact path with forward slashes |
| Web import does not offer ZIP or DAE | The active SketchUp plan or current web workflow does not expose that format | Use an eligible SketchUp plan or perform the Desktop import |
Know what transfers—and what does not
| Information | SketchUp handoff behavior |
|---|---|
| 3D geometry | Generated deck, framing, support, stair, rail, house, finish, roof, screen, ground, and reference geometry transfers when applicable |
| Hierarchy | Semantic category groups and reusable component nodes for equal repeated leaf parts transfer; optional Desktop cleanup is only a fallback when those nodes import as ordinary groups |
| Materials | Supported colors, opacity, UV placement, and packaged image textures transfer as visual approximations |
| Scale | The DAE declares foot units and is intended to import at full model scale |
| Plan information | Dimensions, plan callouts, notes table, schedules, construction details, takeoff explanations, and PDF sheets do not transfer |
| SketchUp presentation | Scenes, section planes, styles, shadows, render settings, and Layout pages must be created in SketchUp after import |
| Ongoing edits | There is no round-trip or live synchronization; changes made in SketchUp do not update DeckDraft, and later DeckDraft revisions require a new handoff |
| Approval status | The visual model does not add engineering, code approval, field verification, or manufacturer approval |
Still unclear?
Ask Docs AI about this page, or open DeckDraft when you need AI Help to read the active job.