Cut List Optimizer Integrations: SketchUp, CAD & Design Software
Short answer: no mainstream cut list optimizer imports a native SketchUp, AutoCAD, or Fusion 360 file directly, but you almost never need it to. Every one of those programs can export a parts list as a CSV, and any decent optimizer - including CutPlan - can read that CSV in seconds. The real integration is not a magic plugin, it is a clean, well-formatted parts table. Get the export right and the transfer takes under a minute with zero retyping. This guide walks through each design tool, the exact columns you need, a worked example, and the small formatting mistakes that quietly ruin a sheet of plywood. For the fundamentals behind the layouts themselves, start with our complete guide to cut list optimization.
Why the gap exists in the first place
Your design software already knows every dimension in your project. Your optimizer knows how to pack those parts onto stock sheets with minimal waste. The trouble is that they speak different languages. A 3D model is a tree of components, faces, and materials; an optimizer wants a flat table of rectangles with a length, a width, a quantity, and a material. Bridging the two by hand means copying four or five values for every part, and one transposed digit (900 typed as 90) can throw off an entire cutting plan.
CSV is the bridge that removes the typing. It is boring, universal, and reliable, which is exactly why it wins. Almost every CAD program and spreadsheet on earth can write a CSV, and almost every optimizer can read one. The extraction step differs by tool; the import step is the same everywhere.
SketchUp: the smoothest path
SketchUp is the most popular modeling tool among woodworkers, and it has the best integration story thanks to one free, open-source extension: OpenCutList. It reads your model and produces a full parts list with dimensions, material assignments, grain direction, and edge banding, all pulled from components you already built.
OpenCutList also ships a basic built-in cutting diagram, and for a simple bookshelf on a single sheet size that is genuinely enough. Where it runs out of room is the messy real world: several stock sizes at once, leftover offcuts you want to reuse, precise saw kerf per material, and grain locking on visible faces. For those, export the list and let a dedicated engine solve the packing.
The SketchUp to CSV to CutPlan workflow
- Model as usual - build each part as a proper component and assign a material to it. OpenCutList only sees parts you have defined as components or groups.
- Run OpenCutList - open the Cutlist tab, let it analyze the model, and skim the result. Confirm dimensions and, for anything with visible figure, check the grain arrows.
- Export as CSV - use the export button and keep the columns simple: name, length, width, quantity, material.
- Import into CutPlan - open CutPlan, choose CSV import, and drop the file. Parts populate instantly.
- Optimize - set your sheet sizes and kerf, then run. You get layouts with grain respected, kerf compensated, and offcuts tracked.
New to the optimizer side? The cut list optimizer tutorial walks through kerf, stock setup, and reading the diagram step by step.
AutoCAD and Fusion 360
AutoCAD has no woodworking-specific cut list, but the DATAEXTRACTION command is the workaround. Draw each part as a block, attach attributes for length, width, and material, then run the wizard and point it at a CSV. Once your blocks are set up, re-extraction on the next project is a two-minute job.
Fusion 360 exposes a Bill of Materials that lists every component with its bounding dimensions. Export the BOM to CSV, rename the headers to match your optimizer (name, length, width, quantity, material), and import. Fusion is excellent at CNC toolpaths for individual parts, but it does not nest many parts across full sheets efficiently, so hand that job to a dedicated nesting or cut list tool. A common gotcha: Fusion often reports a bounding box, so a part modeled with a rabbet or chamfer can export slightly oversized. Trust your model dimensions over the auto BOM when they disagree.
Export formats at a glance
Here is what each common tool gives you and how much cleanup to expect before import.
| Design tool | How you get a parts list | Export format | Cleanup needed |
|---|---|---|---|
| SketchUp + OpenCutList | Cutlist tab, one click | CSV (already labeled) | Minimal - it is built for this |
| AutoCAD | DATAEXTRACTION on part blocks | CSV / XLS | Medium - set up block attributes once |
| Fusion 360 | Bill of Materials export | CSV | Medium - rename headers, check bounding sizes |
| SolidWorks / Inventor | BOM table save-as | CSV / Excel | Medium - trim non-panel rows |
| FreeCAD | Spreadsheet workbench or manual table | CSV | Higher - more hand assembly |
| Any tool + Google Sheets | Type or paste the list | CSV | None once typed |
A worked example
Say you modeled a simple 800 x 600 mm wall cabinet in 18 mm birch ply. After OpenCutList runs, your exported CSV should look like this - clean headers, one row per unique part, quantity doing the multiplication:
| name | length | width | qty | material | grain |
|---|---|---|---|---|---|
| Side | 800 | 300 | 2 | Birch 18mm | length |
| Top/Bottom | 564 | 300 | 2 | Birch 18mm | length |
| Shelf | 560 | 280 | 1 | Birch 18mm | length |
| Back | 800 | 564 | 1 | Birch 6mm | none |
Four rows, six boards in total, and two materials, and the optimizer handles the rest. Note the top and bottom are 564 mm long because two 18 mm side walls eat 36 mm off the 600 mm carcass width - that math comes straight from the model, which is exactly why exporting beats retyping. Drop this into CutPlan, set an 810 x 610 mm offcut plus a full 2440 x 1220 sheet, add a 3 mm kerf, and you get a layout that keeps the birch grain running vertically on both visible sides.
Common mistakes that break the import
Ninety percent of failed imports come from a handful of formatting issues, not from the optimizer. Watch for these:
- Mixed units. Some tools export millimeters, some inches, some a bare number with no unit. Decide on one and confirm the optimizer is set to match before you read the results.
- Comma decimal separators. European locales write 12,5 instead of 12.5. In a comma-delimited CSV that splits one value into two columns and shifts every field after it. Switch to a period decimal or export as semicolon-delimited.
- Quantity baked into rows. If your BOM lists the same shelf four times as separate rows instead of qty 4, clean it up or let the optimizer dedupe, but check it did.
- Header names the importer does not recognize. "Cutting Length (mm)" may not map to length automatically. Rename headers to plain words.
- Assembly and hardware rows. A full BOM includes hinges, screws, and sub-assemblies. Delete anything that is not a flat panel before importing.
- Grain direction dropped. If grain matters, keep the column and set it explicitly. A blank grain field usually means the optimizer is free to rotate parts, which can flip visible figure sideways.
Tip: Open the CSV in a spreadsheet before importing and eyeball it. If every row has a sensible name, two dimensions, a whole-number quantity, and a material, it will import cleanly. If a column looks jumbled, you almost certainly have a delimiter or decimal problem, not an optimizer problem.
Cabinet-specific software
If you live in cabinetry, you may already run software with optimization built in. The main players:
- PolyBoard + OptiCut - PolyBoard designs the cabinet and hands parts straight to OptiCut. Tight integration, but both are paid.
- Cabinet Vision - an all-in-one for large shops covering design, nesting, and CNC output. Pricing starts around $5,000.
- KCD Software - integrated design and optimization for pro shops, roughly $500 to $2,000.
These are capable but expensive, and they lock you into one ecosystem. For most woodworkers - hobbyists, small shops, and plenty of mid-size ones - free SketchUp plus a free-tier optimizer gets you most of the way there. What you give up is the fully automated design-to-CNC pipeline. If you are weighing browser tools against installed software, our online vs desktop comparison breaks down the cost and workflow tradeoffs, and the best cut list optimizer software in 2026 roundup covers the field.
When you should skip integration entirely
Not every job needs a pipeline. Sometimes setting up an export costs more time than it saves:
- Under 20 parts. Typing fifteen panels into the optimizer takes about two minutes. Wiring up a clean CSV export can easily take longer.
- One-off builds. If you are cutting a single bookshelf from a sketch on paper, just key the dimensions in directly and cut.
- Repeat designs. If you build the same carcass again and again, save it as a reusable project, load it, tweak the sizes, and re-run. No CAD round trip needed.
- Quick estimates. When a client asks how many sheets a job will take, a rough parts list gets you a sheet count in seconds without touching the 3D model.
The point is to save time, not to build process for its own sake. Reach for the export when it earns its keep, and skip it when typing is simply faster.
Import your parts list today
Export your SketchUp or CAD parts as CSV, drop the file into CutPlan, and get optimized cutting layouts in seconds. Free for 30 calculations per month.
Open Optimizer →Frequently asked questions
Can I import a SketchUp model directly into a cut list optimizer?
Not directly into most optimizers. Install the free OpenCutList extension for SketchUp, let it extract your parts list, export that list as CSV, then import the CSV into CutPlan or any other optimizer. The whole handoff takes under a minute.
What is the best free workflow for SketchUp plus cut list optimization?
SketchUp Free for modeling, the OpenCutList extension to generate the parts list, and CutPlan's free tier to solve the layouts. The full chain costs nothing and covers most hobbyist and small-shop projects.
Does CutPlan integrate directly with CAD software?
CutPlan imports CSV, which works with any tool that can export a parts list, including SketchUp, AutoCAD, Fusion 360, SolidWorks, and FreeCAD. Direct CAD plugins are on the roadmap, but for now the CSV route already takes about a minute.
Why does my imported CSV look scrambled across the wrong columns?
Almost always a delimiter or decimal problem, not an optimizer bug. A comma decimal like 12,5 splits into two columns inside a comma-delimited file and shifts every field after it. Switch your export to a period decimal or a semicolon delimiter and the rows line up.