ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.

Last updated:

Guided workflow variation

Cabinet cut list softwarebuilt for the order that changes.

Start from the parts list you already keep in a spreadsheet. CutPacket prints a complete cutting packet for the shop floor, and when the client revises the job, it tells the operator which pieces to recut and which to keep.

For a small cabinet shop that keeps parts in a spreadsheet, CutPacket turns the CSV into diagrams, labels, and a recut list, bought once in the Microsoft Store.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Full CutPacket overview
One-time purchase No telemetry Local-first

windows · csv files never changed · nothing uploads · 15-day free trial

If this sounds like your week

The parts list lives in a spreadsheet. The shop floor needs paper.

A small shop usually keeps its cabinet parts list in a spreadsheet: a line for every component with its length, width, quantity, and material. Turning that file into something useful on the floor means sketching layouts on graph paper, tallying how many full sheets of each stock to buy, and hand-lettering a name onto every component.

Where tooling usually breaks

Then the client changes the order.

A homeowner changes their mind midway. One unit gets wider, a drawer bank disappears, and a section of the job is finished. Starting over reshuffles all the layouts and names, so the crew loses track of which stacked components remain usable. Effort is repeated, outdated parts end up in assemblies, and the muddle returns with each change.

Where CutPacket lands

One packet, and a recut list for every revision.

CutPacket imports the CSVs you already keep, flags anything that would spoil material, and lays out each sheet for you to review and approve. Then it exports diagrams, labels, and spreadsheets in one step. When the order changes, IDs hold steady and the recut list names exactly what to redo.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Learn more about CutPacket

windows · csv files never changed · nothing uploads · 15-day free trial

What you get

Feature highlights

A recut list for every revision

import the revised parts CSV and every piece gets one action, Cut, Recut · scrap old, Cut as planned, Keep, or Surplus, with its sheet and reason, and pieces already cut and unchanged use no new stock.

Stable part IDs

the ID in your CSV is the label on the piece, with -1, -2 for multiples, and matching IDs keep their labels from one revision to the next.

Kerf, edge trim, and grain

set the blade kerf and edge trim in millimetres or inches, and parts marked length or width follow the grain on grained stock while parts on melamine or MDF rotate to fit.

Layouts a panel saw can follow

every sheet is built from straight, edge-to-edge rips and crosscuts, printed in order with their positions, and the same inputs give the same layout every time.

Checked before the saw

mixed units, blank grain on grained stock, oversize parts, unknown materials, duplicate IDs, and short stock are listed with the CSV row and the fix before you generate.

A complete packet, nothing uploaded

cut diagrams, 4 × 2 inch labels, and the recut list as PDF and CSV in a new folder for each revision, while your CSV files stay unchanged on your PC.

Especially when

  • Turn a parts spreadsheet into sheet layouts, cut diagrams, and labels without drawing on graph paper or retyping the list
  • Know which already-cut pieces to keep, recut, or set aside when a client revises the order mid-job
  • Catch mixed units, missing grain, oversize parts, and short stock before a sheet goes on the saw
  • Keep part labels stable across revisions so the pieces on the cart still match the new paperwork

Who benefits

Real-world scenarios

A two-person cabinet shop

The owner builds every job’s parts list in a spreadsheet and used to sketch sheet layouts on graph paper the night before cutting, then write part names on each piece with a marker.

Now the owner saves the sheet as CSV, imports it with the stock list, fixes the rows the validation list flags, chooses Generate packet, approves each sheet, and hands the operator printed diagrams and a stack of labels.

Veneered ply and melamine in one job

Carcass sides must keep the face grain vertical on prefinished maple ply, but drawer boxes in white melamine can turn whichever way fits the sheet.

Parts marked grain length stay along the sheet length on the maple ply, and the melamine parts rotate freely because that stock is marked grain no. Each material gets its own sheets, and the summary page lists how many of each to pull.

Testing it on a job that already changed

Before buying, a production lead wants to see what the app would have said about last month’s kitchen, which the client revised after the first sheets were cut.

During the 15-day free trial the lead imports the original parts CSV, ticks the sheets that were cut, imports the revised CSV, and compares the recut list with what the shop actually redid.

Deep dive

What to look for in cabinet cut list software

It reads the list you already keep. Retyping a parts list into a new program is where mistakes start. CutPacket imports a parts CSV and a stock CSV saved from Excel or any spreadsheet. It recognizes common header names, such as part, part_no, or code for the ID and qty, pcs, or pieces for the quantity, detects comma, semicolon, or tab delimiters, and reads sizes written as 610, 610mm, 24in, 24", or 24 1/2.

It stops a bad sheet before it is cut. A millimetre value imported as inches, a part with no grain on grained stock, or a part bigger than any sheet should never reach the saw. CutPacket lists each problem as an error or a warning with the CSV row, the part ID, and the fix, and Generate packet waits until the errors are cleared.

Layouts a panel saw can follow. Cabinet parts are rectangles cut with straight saw cuts. CutPacket lays out every sheet as a guillotine layout, so each cut runs edge to edge across the panel in front of the operator, and it numbers the rips and crosscuts in order. The kerf comes out between pieces, and the edge trim cleans the factory edge before anything is placed.

Labels that match the parts list. The ID in your CSV is the label on the piece, with -1, -2 added for multiples. Every label also shows the name, size, material, grain, sheet, and saw number, so a stacked piece can be traced back to its cabinet.

A plan for revisions. This is the step most cut list tools leave to you. Look for a tool that compares the new list with the old one by part ID, knows which pieces the shop has already cut, and tells the operator what to recut, what to keep, and what to set aside. In CutPacket that is the recut list, and it comes out of the same export as the diagrams.

A file you can reopen. A job is not finished when the first packet prints. CutPacket saves the parts, stock, saw settings, approvals, pins, and already-cut ticks in a .cutpacket project file, so the next revision starts where the shop left off.

Try it on your own job. The Hartley kitchen sample job opens on first run with a real revision, and the Microsoft Store runs a 15-day free trial, so you can run one of your own past jobs through CutPacket before you buy.

How it is built

Built so the shop always knows which piece is which.

Stable part IDs

The ID in your CSV is the label on the piece. Revisions are compared by ID, so the labels on the cart still match the new paperwork, and row order never matters.

Cuts a saw can make

Every layout is built from straight, edge-to-edge rips and crosscuts with your kerf, trim, and grain, and the same inputs give the same layout on every run.

Nothing uploads

No account, no telemetry, and no network calls of its own. CSV files are only read, and each packet goes to a new folder. One-time purchase in the Microsoft Store.

Head-to-head

How CutPacket compares

Feature CutPacket Spreadsheet by hand Online optimizer Cabinet design suite
Starts from your parts CSV Yes, with headers like id, part, qty, or pcs recognized The list is there; layouts are drawn by hand Often typed or pasted into a web form Parts come from the cabinets you draw in it
Kerf, edge trim, and grain Set once per job; grain checked on every part Worked out by hand Varies by site Yes, inside the suite
Recut list for a revised order Yes: Cut, Recut · scrap old, Cut as planned, Keep, and Surplus Compared row by row by hand A new layout from scratch Varies; often a new cut list
A label for each piece 4 × 2 in labels with ID, size, grain, sheet, and saw number Written on the piece with a marker Varies by site Yes, often with its own printer setup
Where the job data goes Stays on this PC. Nothing uploads. Stays on this PC Uploaded to the site Depends on the suite
How it is paid for One-time purchase in the Microsoft Store Your evenings Per use or per plan Often a yearly license or subscription

FAQ

Straight answers—no glossary dump

What should cabinet cut list software do?

At minimum, it should turn a parts list into sheet layouts with kerf, edge trim, and grain applied, and print something the saw operator can follow. For a working shop it should also check the list for unit and grain mistakes, label every piece, and handle revisions without reshuffling labels. CutPacket does all of that on Windows, starting from the parts and stock CSV files you already keep.

What do I need before I start?

A parts list and a stock list saved as CSV from Excel or any spreadsheet. The parts file needs an ID, a length, a width, and a material on each row; quantity, name, grain, unit, and notes are read when present. The stock file lists each sheet size with its material, the number on hand, and whether it has grain. The Hartley kitchen sample job shows both formats.

How is CutPacket sold?

As a one-time purchase in the Microsoft Store, which shows the current price in your currency and runs a 15-day free trial. The Store installs and updates the app, and there is nothing to activate inside CutPacket. Every job, project file, and packet stays on your PC, and the app works with no account.

What happens to my CSV files and earlier packets?

They stay exactly as they are. CutPacket reads your parts and stock CSV files and never writes to them. Each export creates a new folder named after the job and revision, such as Hartley-kitchen-base-run_rev2, inside a folder you pick. If that folder already holds a packet, the new one is written beside it with a -2 suffix, so the packet the shop is cutting from stays intact.

Where does my job data go, and how do I get CutPacket?

It stays on your PC. CutPacket has no account, collects no telemetry, and makes no network calls of its own. It reads the CSV and project files you pick and writes each packet to the folder you choose. CutPacket is a one-time purchase in the Microsoft Store, which runs a 15-day free trial, and it runs on Windows 10 version 2004 or later and Windows 11.

A parts CSV in.
Cut diagrams, labels, and a recut list out.

CutPacket lays out every sheet with your kerf, edge trim, and grain, prints a label for every piece, and writes a recut list when the order changes, keyed by the part IDs in your CSV. Your CSV files are never changed, nothing uploads, and the Microsoft Store runs a 15-day free trial.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Open full product page

Avery is a trademark of its owner. CutPacket is not affiliated with or endorsed by Avery.

Technical specifications

Technical specifications for procurement

Spec Implementation
Data Sovereignty Reads only the parts CSV, stock CSV, and .cutpacket project files you pick, and never writes to the CSV files; writes each packet to a new folder you choose and project files where you save them; settings and a small diagnostic log stay in the app’s local data folder on this PC
Telemetry Status None; no account, no telemetry, and no network calls of the app’s own (the Microsoft Store handles purchase and the trial)
Core Runtime .NET 10 and WPF desktop app; PDFs are drawn on your PC with the fonts embedded, so they print the same from any PC
Network Requirements Fully functional offline; the app makes no network calls of its own
Deployment Compatibility Windows 10 version 2004 or later and Windows 11, x64; runs as a standard user with no elevation; one-time purchase in the Microsoft Store with a 15-day free trial
Inputs Parts and stock lists as CSV (comma, semicolon, or tab; UTF-8 with or without BOM); common header names recognized; millimetres or inches from a unit column, a header suffix, or a value suffix, with fractions such as 23 1/4
Validation Mixed or unknown units, sizes over 10 m, duplicate or missing IDs, blank grain on grained stock, oversize parts after trim, unknown materials, stock area shortfall, and unusual kerf, each with the CSV row and the fix
Layout Guillotine layouts (straight, edge-to-edge rips and crosscuts) with kerf and edge trim; grain per part (length, width, none) and per sheet (yes, no); several strategies per run, deterministic for the same inputs; sheet pins and per-sheet approval
Revisions Parts compared by stable ID; already-cut pieces ticked per piece or per sheet; recut actions Cut, Recut · scrap old, Cut as planned, Keep, and Surplus; kept pieces left out of the new layout
Outputs Cut diagrams PDF (summary plus one landscape page per sheet with the cut sequence), labels PDF (4 × 2 in, 10 per US Letter page, Avery 5163 layout), recut list PDF, cut list, labels, and recut list CSVs (UTF-8 with BOM), and the plan as JSON
Projects .cutpacket project file with parts, stock, saw settings, plan, pins, approvals, the previous revision, and already-cut ticks; a sample job with a real revision is included