Cut List Optimizer vs Excel: When a Spreadsheet Isn't Enough

Excel is the first tool most people reach for when they need to organize a cut list. It makes sense — you already know how to use it, it's on every computer, and a table of parts with dimensions feels like a spreadsheet problem. Until you try to figure out how those parts fit on a sheet. That's where Excel hits a wall.

Every woodworking forum, every fabrication Q&A board, every Excel help community has the same thread. Someone posts a spreadsheet with part names, lengths, widths, and quantities. Then they ask: "How do I get Excel to tell me the most efficient way to cut these parts from my stock sheets?"

The answers range from "use Solver" to "write a VBA macro" to "you can't — use dedicated software." The truth is somewhere in between, and understanding exactly where Excel stops being useful is the key to deciding when you need a real cut list optimizer.

What Excel Does Well

Let's give Excel its due. For the first stage of cut list planning — building the parts list itself — Excel is perfectly fine. In fact, it's good.

You can list every part with its name, length, width, thickness, quantity, material type, grain direction, and notes. You can use formulas to calculate total area, total edge banding length, and estimated material cost. You can sort, filter, and group parts by material or by cabinet. You can share the spreadsheet with your team.

If all you need is a parts list — a structured table of what to cut — Excel does the job. This is why CutGrid (and most other cut list optimizers) let you import directly from Excel and CSV. The spreadsheet is a great place to build your list. It's just not the right place to optimize your layout.

Where Excel Breaks Down

The moment you ask "how should I arrange these parts on my sheets?", you've left the territory of spreadsheet formulas and entered the territory of combinatorial optimization. Here's why that matters.

The 2D nesting problem is NP-hard

This isn't just jargon — it has a practical meaning. "NP-hard" means that the number of possible arrangements grows so fast that no computer can try them all in a reasonable time, even for modest inputs.

Take a simple example: 20 parts on a single sheet. Each part can be placed at any position, and most can be rotated 90°. The number of possible arrangements is astronomical — far more than the number of atoms in the universe. Finding the best one requires specialized algorithms that intelligently search the solution space using heuristics, not brute force.

Excel's Solver add-in can handle simple linear optimization problems. But 2D bin packing with rotation, kerf gaps, grain direction, and multiple sheets is not a linear problem. Solver either can't model it at all, or it runs for hours and produces a mediocre result.

No visual layout

Even if you somehow calculated an optimal arrangement in Excel, you'd still need to draw it. A cut list optimizer produces a visual cutting diagram — a color-coded map showing exactly where each part sits on each sheet, with dimensions, part labels, and cut sequence. This is what you print and take to the saw.

In Excel, you'd need to manually draw rectangles in a chart or an external drawing tool. For every sheet. Every time you change a dimension or add a part.

No kerf compensation

When a saw blade passes through material, it removes a strip of material — the kerf. A typical panel saw kerf is 3 – 3.5 mm. A cut list optimizer inserts this gap between every pair of adjacent parts automatically.

In Excel, you'd need to manually add kerf allowances to every dimension calculation. If you have 40 parts across multiple sheets, that's dozens of extra formulas — each one a potential error. And if you change the kerf value (because you switched blades), you'd need to update every formula.

No algorithm choice

A dedicated optimizer lets you choose between Guillotine and Standard (Shelf) algorithms depending on your equipment. Guillotine ensures every cut goes edge to edge (for panel saws). Standard allows flexible placement (for CNC). Excel doesn't know what a guillotine cut is.

No multi-sheet optimization

Real projects use multiple sheets. A 40-part kitchen cabinet project might need 3 – 4 sheets of MDF. The optimizer decides which parts go on which sheet to minimize total waste across all sheets — not just on one sheet at a time.

In Excel, you'd need to manually assign parts to sheets, then manually check if they fit, then manually rearrange when they don't. Change one dimension and the entire assignment might need to be redone.

No offcut tracking

When you finish cutting a sheet, you're left with offcuts — usable pieces of material that are too small for the current project but might be perfect for the next one. A cut list optimizer tracks these offcuts in your stock library and reuses them in future projects.

Excel doesn't know your offcuts exist.

The VBA Macro Approach

Some resourceful users have written VBA macros that attempt basic 1D cut optimization in Excel. These work for linear materials — cutting lengths from a bar or pipe — where the problem is one-dimensional.

A typical VBA approach sorts parts by length (longest first), assigns them to stock lengths using a first-fit decreasing algorithm, and reports the total stock needed and the waste per bar. For simple linear cutting — aluminium profiles, timber studs, steel pipes — this can work reasonably well.

But there are significant limitations:

1D only. VBA macros for 2D sheet nesting are extremely rare and extremely fragile. The algorithm complexity jumps dramatically when you add a second dimension, rotation, and kerf.

No visual output. The macro gives you a text list — "Bar 1: cut 2400, cut 1800, waste 300" — but no diagram. You have to mentally reconstruct the layout, which invites errors.

Fragile code. VBA macros break when you change the spreadsheet structure, rename columns, or open the file in a different version of Excel. They're difficult to debug and impossible to maintain unless you wrote them yourself.

No kerf, no trim, no grain. Most VBA macros ignore saw kerf, sheet trim margins, and grain direction. Adding these parameters makes the code significantly more complex — and most users who can write that level of VBA would be better served writing a standalone application.

Performance. VBA is slow. A complex 2D optimization that takes CutGrid under a second could take a VBA macro minutes — or crash Excel entirely.

The Solver Approach

Excel's built-in Solver is a legitimate optimization tool. It can solve linear programming problems, and it has an evolutionary solver for nonlinear problems. Some users have tried to model cut list optimization using Solver.

The setup is complex: you define decision variables (where each part is placed), constraints (no overlap, within sheet bounds, kerf gaps), and an objective function (minimize waste). For very small problems — 5 to 8 parts on a single sheet — Solver can sometimes find a reasonable solution.

For anything larger, Solver hits its limits. The free version is limited to 200 decision variables. Even the paid version (OpenSolver or Solver add-ins) struggles with the nonlinear constraints of 2D packing. And you still don't get a visual layout — just a table of coordinates.

Real-World Comparison: Same Project, Two Tools

Let's make this concrete. You're building a set of five bookshelves from 18 mm birch plywood. Stock sheet: 2440 × 1220 mm. Kerf: 3 mm. Trim: 10 mm.

Your cut list:

Total: 50 parts.

In Excel: You list the parts (2 minutes). You calculate the total area of all parts: roughly 10.2 m². Each sheet is 2.98 m². So you need at least 3.4 sheets — meaning 4 sheets minimum, probably 5 once you account for kerf and trim. But how many do you actually need? You don't know, because you can't see how the parts fit. You might guess 5 or 6 sheets and buy accordingly. If you guess wrong, you're back at the lumber yard.

In CutGrid: You enter the same parts (or import the Excel file — 30 seconds). You set the kerf to 3 mm and trim to 10 mm. You hit Optimize. In under a second, CutGrid produces a layout: 4 sheets, 86% material utilization, with a clear diagram showing exactly where each part goes. You export the PDF and walk to the saw.

The difference: Excel told you "probably 5 sheets, maybe 6." CutGrid told you "exactly 4 sheets, here's how to cut them, and here are the leftover offcuts you can save." One sheet saved, $40 – $80 back in your pocket.

When Excel Is Still the Right Choice

To be fair, there are situations where Excel is genuinely sufficient:

You're building a parts list, not optimizing. If you just need to list parts with dimensions and calculate material area, Excel is fine. Then import that list into CutGrid for the optimization step.

You have 5 or fewer parts. If you're cutting a small shelf or a simple box, you can probably arrange the parts on a sheet in your head. An optimizer adds unnecessary complexity for trivial projects.

You're doing 1D linear cutting with a simple macro. For cutting lengths from bars or pipes — where the problem is one-dimensional and you have a working VBA macro — Excel can produce reasonable results. The gap between a simple VBA macro and a dedicated linear optimizer is smaller than the gap in 2D sheet optimization.

You're in the field and only have your phone. A quick spreadsheet on Google Sheets to estimate material quantities is better than nothing. But CutGrid runs in any browser too — including your phone — so this advantage is disappearing.

The Hybrid Workflow: Excel + Optimizer

For many workshops, the best approach combines both tools. Here's a workflow that works:

Step 1: Build your cut list in Excel. Use the spreadsheet for what it's good at: organizing data. List parts, calculate quantities, track materials, estimate costs. If you have a template you've been using for years, keep using it.

Step 2: Import into CutGrid. Save your Excel file as .xlsx or .csv. Import it into CutGrid. The parts, dimensions, quantities, and material types transfer directly — no re-typing.

Step 3: Optimize and export. Set your kerf, trim, and algorithm. Run the optimization. Export the cutting diagram as a PDF for the shop floor, or as DXF for your CNC.

Step 4: Update your Excel file. After optimization, export the results back to Excel if you need the data in your existing workflow — cost reports, purchase orders, inventory updates.

This workflow respects your existing process while adding the one thing Excel can't do: spatial optimization.

The Math Behind Why Spreadsheets Can't Compete

If you're curious about why this problem is so hard for a spreadsheet, here's the intuition.

For a 1D problem (cutting lengths from a bar), the number of possible arrangements grows factorially — 20 parts have 20! (about 2.4 quintillion) possible sequences. But good heuristics like first-fit decreasing can solve this efficiently because they only need to decide which bar each length goes on.

For a 2D problem (cutting rectangles from a sheet), each part has an X position, a Y position, and a rotation. The constraints (no overlap, within bounds, kerf gaps) create a complex geometric problem that can't be reduced to a simple sequence. The number of decision variables grows as 3n (three variables per part), and the constraints grow as n² (every pair of parts must not overlap).

With 50 parts, that's 150 decision variables and 2,500 non-overlap constraints. Excel's Solver is designed for problems with dozens of variables, not hundreds. And even if it could handle the size, the geometric constraints are nonlinear — they involve "either/or" conditions that Solver handles poorly.

This is why dedicated cut list optimizers exist. They use specialized algorithms — shelf heuristics, genetic algorithms, simulated annealing, and hybrid approaches — that are purpose-built for this exact class of problem. They find near-optimal solutions in seconds, not hours.

Key Takeaways

Excel is excellent for building a parts list. Keep using it for data entry, calculation, and organization. It's the best spreadsheet tool in the world for a reason.

Excel is not a layout optimizer. The moment you need to decide how parts fit on sheets, you need a different tool. The 2D nesting problem is mathematically hard — too hard for Solver, too hard for VBA macros, and too visual for a grid of cells.

The real waste isn't in the software cost — it's in the extra sheets. A CutGrid subscription costs less than a single sheet of birch plywood. If the optimizer saves you even one sheet per project, it pays for itself immediately.

Import, don't re-type. CutGrid reads Excel and CSV natively. Your spreadsheet is the input; the optimizer is the engine; the cutting diagram is the output.

Still Using Excel for Your Cut Lists?

Import your spreadsheet into CutGrid and see the difference. Your parts list stays the same — you just get a smarter layout.

Import Your Excel File Free →