SketchUp cabinet design: kitchens, doors and cut lists
Build every cabinet from components, one per board, so identical parts count together and the cut list comes out right. For a ready-made cabinet library use an extension such as CabMaker. For your own shop's rules (door splits, reveals, face frames) you can write Dynamic Component formulas, or have a short Ruby script build the box from numbers.
Four ways to draw cabinets in SketchUp
Most shops end up mixing these. Which one fits depends on how standard your cabinets are and how often you redraw the same box.
- By hand, with components. Draw each side, bottom, rail and back as its own component. Slow for a whole kitchen, but you control every joint, and it's how most people learn.
- Dynamic Components. Trimble's Live Components include some cabinets, and you can write your own. The catch is the formulas: a door that splits in two past 600 mm, or a face frame with a mid-stile, takes nested IF formulas that break in ways that are hard to trace.
- Cabinet extensions. GKWare CabMaker is the one forum users recommend most for kitchens and vanities. ABF and 3H furniture also come up, and some of these output CNC data. Extensions need desktop SketchUp Pro, and some only run on Windows, so check the Extension Warehouse listing before you buy.
- A script. A short Ruby script can build a box from a few numbers using your own rules. There's an example below, and an AI agent can write and adjust one for you.
If you cut on a CNC every day, dedicated cabinet software such as Cabinet Vision or Mozaik still runs the production side for most shops. SketchUp is strongest at the design stage: client drawings, layout options and checking that a run fits the room.
How to model a cabinet so it works in the shop
A cabinet that looks right isn't enough. If you want counts, a cut list or drawings out of the model, it has to be built the way the shop thinks about it.
- One board, one component. Sides, bottom, rails, back, shelves and doors each get their own component. Then copies share one definition, and the cut list shows "Side × 2" instead of two lines.
- Name parts by what they are and their size. "Side 18x560x720" reads well on a shop list and stays distinct from a deeper side. See renaming components to fix a model full of "Component#14".
- Material on the component. Paint the part with 18 mm birch ply or white oak, not the individual faces, so cut list tools can sort by material. Swapping a material everywhere is easy later if the client changes their mind.
- Axes along the grain. Set each part's red axis along the grain so length and width come out the right way round. The cut list guide shows how.
- A tag per part type. Carcass, doors, drawer fronts, hardware, countertop. Turning a tag off is how you show a client the inside, without keeping a second copy of the kitchen.
- Group the whole cabinet and name it by its width, so a run of 600, 900 and 600 bases is easy to read in the Outliner.
Laying out a kitchen run
- Draw the room from your site measure: walls, window and door openings, and anything fixed like a soil stack or a boxed-in beam.
- Place the appliances first, at their spec-sheet sizes, with the clearances the manufacturer asks for.
- Fill each wall with standard widths (300 to 900 mm, or 12 to 36 in), then take up what's left with fillers, not odd-sized boxes.
- Check the corners: door swings, drawer and handle clearance, and blind-corner access.
- Make a scene for each wall with Camera › Parallel Projection for flat elevations, plus a perspective view for the client.
Kitchen designers often duplicate a whole drawing just to show it with the doors on and off. Put the doors and drawer fronts on their own tag instead, and save one scene with that tag hidden. Each scene remembers its tag visibility, so the two views stay in step when you change the layout.
Doors that split by width: formulas, a script or one sentence
A common shop rule: a door wider than 600 mm becomes two equal doors, with a 2 mm reveal all round. In a Dynamic Component this means a door count worked out from the carcass width, a hidden attribute for each leaf and a position formula for each one. It works until you swap the definition and every instance resets to its original size, which is one of the most common complaints in cabinet threads on the SketchUp forum.
Outside Dynamic Components you have two options. You can run a short script yourself, or describe the cabinet to an AI agent and let it write and run the script for you.
Option 1: run the script
This script builds a 900 mm base cabinet in 18 mm board with a 6 mm back, two top rails and overlay doors. The door rule is a single line. Change the numbers on the first two lines for a different box.
# One base cabinet: sides, bottom, top rails, back and doors, each part a component.
# Sizes in mm. Doors split into more leaves whenever one would be wider than max_door.
w, h, d, t = 900.mm, 720.mm, 560.mm, 18.mm # width, height, depth, board thickness
back, reveal, max_door, rail = 6.mm, 2.mm, 600.mm, 100.mm
model = Sketchup.active_model
model.start_operation("Base cabinet", true)
cab = model.active_entities.add_group
cab.name = "Base cabinet #{w.to_mm.round}"
# Parts with the same name and size share one definition, so a cut list counts them together.
part = lambda do |name, x, y, z, pw, pd, ph|
label = "#{name} #{pw.to_mm.round}x#{pd.to_mm.round}x#{ph.to_mm.round}"
defn = model.definitions[label]
unless defn
defn = model.definitions.add(label)
face = defn.entities.add_face([0, 0, 0], [pw, 0, 0], [pw, pd, 0], [0, pd, 0])
face.reverse! if face.normal.z < 0
face.pushpull(ph)
end
cab.entities.add_instance(defn, Geom::Transformation.new([x, y, z]))
end
inner = w - 2 * t
part.call("Side", 0, 0, 0, t, d, h)
part.call("Side", w - t, 0, 0, t, d, h)
part.call("Bottom", t, 0, 0, inner, d - back, t)
part.call("Top rail", t, 0, h - t, inner, rail, t)
part.call("Top rail", t, d - back - rail, h - t, inner, rail, t)
part.call("Back", t, d - back, 0, inner, back, h)
leaves = (w / max_door).ceil
door_w = (w - reveal * (leaves + 1)) / leaves
leaves.times do |i|
part.call("Door", reveal + i * (door_w + reveal), -t, 0, door_w, t, h - reveal)
end
model.commit_operation
puts "Built #{cab.name} with #{leaves} door(s), each #{door_w.to_mm.round(1)} mm wide"Paste it into Extensions › Developer › Ruby Console (SketchUp 2021.1 and newer). The Ruby script guide covers saving it as a file instead. It runs as one operation, so a single Edit › Undo removes the whole cabinet.
It's deliberately simple. There's no toe kick, shelf, drawer or hinge boring, and the doors are full overlay. Treat it as a starting point for your own construction rules.
Option 2: paste one sentence to your AI agent
With MakeIt4Me (our product), your AI agent works directly in your open SketchUp model. Instead of the script, paste this:
"Build a 900 mm base cabinet in 18 mm birch ply with a 6 mm back and a 100 mm toe kick. Overlay doors with 2 mm reveals, split any door wider than 600 mm, and add one adjustable shelf."
The agent writes the Ruby, runs it and takes a screenshot to check the result. Because you're describing the cabinet instead of editing code, the toe kick and shelf the script leaves out are just more words in the sentence. For the next box, change the numbers and send it again.
Cut list and sheet count
Because the script names each part by its size, identical parts share a definition and a cut list adds them up. Build three of these cabinets and the list shows "Side 18x560x720 × 6".
For the list itself, the free OpenCutList extension groups parts by material and thickness and draws cutting diagrams, which is how you get a real sheet count for 18 mm ply. The cut list guide walks through it, along with SketchUp's own Generate Report and a script that writes a CSV.
For CNC, OpenCutList's exports or a cabinet extension can feed your CAM software. SketchUp itself doesn't produce G-code.
Describe the cabinet, let an AI agent build it
MakeIt4Me (our product) connects an AI agent on your computer (Claude, ChatGPT desktop, Cursor and others) to your open SketchUp model. You describe the job in shop terms. The agent writes the Ruby, runs it in your model and takes a screenshot to check the result. If a door lands in the wrong place, it sees that and fixes it.
"Build matching wall cabinets above this run, 720 mm tall, with the doors lined up on the base cabinets below."
"Lay out this wall as a 600 base, a 900 sink base and a 600 drawer base, with a 50 mm filler against the corner."
"Make a parallel-projection scene for each wall, and one more with the Doors tag hidden."
"Write a cut list grouped by material, and estimate how many 2440 × 1220 sheets of 18 mm ply it needs." It can only estimate sheets from part areas, so use OpenCutList's cutting diagrams for the real nesting.
Once a cabinet comes out the way your shop builds it, ask the agent to turn the script into a toolbar button, so the next one is a click. See making your own extension. Expect a round or two of corrections the first time.
It doesn't replace CabMaker's library or Cabinet Vision's CNC output. It's for your own construction rules and the repetitive drawing work no extension handles quite the way you do it.
Questions
Is there a free cabinet plugin for SketchUp?
Trimble's Live Components include a set of cabinets, though forum users find it incomplete for full kitchens. ABF is a free extension that comes up in forum threads. For the cut list side, OpenCutList is free and open source.
Can SketchUp send cabinets straight to a CNC?
Not on its own. SketchUp doesn't produce G-code. Extensions such as OpenCutList, or a cabinet extension with CNC output, can export parts for your CAM software, and dedicated cabinet programs handle the whole pipeline.
Should I use SketchUp or dedicated cabinet software?
Many shops use both. Dedicated software such as Cabinet Vision or Mozaik is built around production and CNC. SketchUp is quicker for design options, client drawings and fitting a run to an awkward room, and it's far cheaper.
Why do my Dynamic Component doors lose their sizes?
Swapping or reloading a Dynamic Component definition resets every instance to the definition's original attributes, so doors you'd resized go back to their default sizes. Rules that live in a script are safer: you rerun the script with new numbers instead of editing formulas instance by instance.