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

A label on every piece,in the order it comes off the saw.

Parts pile up fast behind the saw. CutPacket prints one label per piece, ten to a Letter sheet, carrying the ID from your list, the finished size, material, grain, sheet number, and saw number, so every component can be traced to the cabinet it belongs to.

Export the packet and the labels PDF is in it: one 4 × 2 inch label per piece, in saw order, with NEW and RECUT tags in a revision.

Pay once. Own it forever.

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

Get it from Microsoft

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

A stack of panels with no names is a puzzle.

Thirty panels of prefinished ply leave the outfeed table looking much alike: sides, bottoms, stretchers, and shelves, several within a few millimetres of each other. Writing a name on each with a marker slows production, and handwriting is easy to misread at the bench. Once an unnamed panel reaches the edge bander, somebody has to measure it to learn what it is.

Where tooling usually breaks

Handmade tags drift from what was actually cut.

A tag copied by hand from a spreadsheet can disagree with the layout that was actually followed, especially after changes. Two stretchers of identical dimensions from different boxes get swapped, a stale part gets a fresh name, and the error surfaces during assembly when a carcass will not go square.

Where CutPacket lands

Labels printed from the same plan as the cuts.

CutPacket prints its labels from the same layout that drew the diagrams, so each one names its sheet and its place in the cutting order. The large text is the ID from your spreadsheet, with -1, -2 for multiples. After a change, pieces to cut carry a NEW tag, altered ones a RECUT tag naming what to discard, and kept ones need nothing new.

Pay once. Own it forever.

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

Get it from Microsoft

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

Matching pieces at the edge bander

The operator sends a cart of panels to edge banding, and the person at the bander needs to know each piece’s cabinet and size without walking back to the parts list.

Every piece carries its label: the ID, such as B1-SIDE-1, the name from the CSV, such as Base 1 side, then 870 × 580 mm, the material, the grain, and the sheet and saw number. A descriptive name column in the CSV does the explaining.

Labels for a thermal printer

The shop prints its labels on a roll printer whose software takes a CSV file rather than a PDF of label sheets.

Every packet also includes a labels CSV, UTF-8 for Excel, with the label, part ID, name, length, width, material, grain, sheet, saw order, position, rotation, revision action, job, and revision for each piece, ready to map in the printer’s own software.

Reprinting only what a revision needs

After a revision, the cart already holds the labeled pieces from the first sheet, and a full new set would mean peeling and replacing labels that are still right.

The revision’s labels PDF prints only new, changed, and not-yet-cut pieces; pieces already cut and unchanged keep the labels they have. Recut labels carry the change and the note to scrap the old piece with the same ID.

Deep dive

What goes on a cabinet part label, and why

The part ID, large. The first line is the piece’s label in large bold type: the ID from your CSV for a single piece, or the ID with -1, -2, and so on for each piece of a multiple. It is the same text that appears on the diagram, in the recut list, and in every CSV, so one glance links a piece to every document in the packet.

Name and finished size. Under the ID is the part name from the CSV, then the size as length × width in the job’s unit, printed as the part was listed even when the piece was turned on the sheet to fit.

Material and grain. Next comes the material name and the grain: an arrow with length or width for a part that follows the grain, grain any for a part allowed to turn on grained stock, or no grain for stock such as melamine.

Where it was cut. The footer gives the sheet number, the saw number, which is the order the piece came off that sheet, and the job name with its revision, such as Hartley kitchen base run rev 2.

Sheet format. Labels are 4 × 2 inches, two across and five down on US Letter, the same layout as Avery 5163 label sheets. They print in saw order, sheet by sheet, so the labels come off the printer in the order the pieces come off the saw. Each label has a faint outline as a cut guide.

Revision tags. In a revision, a piece to cut gets a NEW tag, and a changed piece that was already cut gets a RECUT tag with the change and the old piece to scrap. Pieces already cut and unchanged keep the labels they carry, so the revision prints none for them.

The same data as CSV. The labels CSV beside the PDF carries the same fields for each piece, plus its position on the sheet and whether it was rotated, for label printers, spreadsheets, and shop software.

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.

FAQ

Straight answers—no glossary dump

What label sheets does CutPacket print on?

4 × 2 inch labels, two across and five down on a US Letter page, the same layout as Avery 5163 sheets. Labels print in saw order, sheet by sheet, from the labels PDF in each exported packet. For a thermal or roll label printer, use the labels CSV in the same folder, which holds the same fields for every piece.

What is printed on each cabinet part label?

The piece’s label in large type, which is the part ID from your CSV with -1, -2 for multiples, then the part name, the size as length × width in the job’s unit, the material, and the grain. The footer gives the sheet number, the saw number, and the job name and revision. Recut labels add the change and the old piece to scrap.

How are labels handled after a revision?

The revision’s labels PDF prints a label for every piece that still has to be cut: new pieces and changed pieces not yet cut get a NEW tag, and changed pieces that were already cut get a RECUT tag with the note to scrap the old one. Pieces already cut and unchanged keep their existing labels, so nothing on the cart needs relabeling.

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.

Related pages

The order changed. Here is what goes back to the saw. A printed diagram for every sheet, with the cut order on the page. Cabinet cut list software built for the order that changes.

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

Get it from Microsoft

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