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

The order changed.Here is what goes back to the saw.

Import the revised parts CSV and CutPacket compares it with the previous revision part by part. Each piece gets one action and a sheet number, so the operator redoes what changed, keeps what is still good, and sets aside what the client dropped.

Tick the pieces already cut, import the revised CSV, and generate: the recut list says what to cut, recut, keep, or set aside, sheet by sheet.

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

Half the job is cut when the new drawing arrives.

Revisions seldom wait for a convenient moment. The client widens a base unit by 100 mm, drops a drawer bank, and adds an end panel after the first sheets are through the saw. Someone must decide which finished pieces survive the change, which are now the wrong size, and what new work comes off which sheet.

Where tooling usually breaks

A fresh layout scrambles the labels on the cart.

Running the optimizer again gives a tidy new plan, but it renumbers everything, so the tags on the cart no longer match the new pages. Comparing two lists by eye misses a stretcher that grew by 100 mm. The result is an unplanned recut, or an outdated piece that slips into the assembly.

Where CutPacket lands

Stable IDs, ticked pieces, and one action per piece.

CutPacket keys each part by the ID in your CSV, so a revision is compared part by part, never line by line. Pieces ticked on the Already cut tab that did not change are kept and left out of the new layout, using no new stock. Changed ones are marked Recut · scrap old, new ones Cut, and removed ones Surplus, each with its reason.

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

A cabinet that got wider

Base 2 grows from 900 to 1000 mm after its bottom and two stretchers were cut, so three finished pieces are now 100 mm short and the back panel has to grow too.

The recut list shows B2-BOT, B2-STR-1, and B2-STR-2 as Recut · scrap old with the change, such as size 864 × 580 mm → 964 × 580 mm, and the larger back as Cut. Their labels print with a RECUT tag and the note to scrap the old piece.

A cabinet dropped from the job

The client drops Base 3 entirely, and its sides, bottom, and stretchers were already cut with the first sheet of maple ply.

All five pieces appear in the Surplus section with the reason Part removed in this revision, so they do not end up in another cabinet by mistake. The summary page counts them alongside the pieces kept and the pieces to cut.

More drawer boxes than planned

The revision adds a second drawer box 3, so its sides and ends go from two pieces each to four, and its bottom from one piece to two.

The pieces already planned stay as they were, and the extra pieces, DB3-SIDE-3, DB3-SIDE-4, DB3-END-3, DB3-END-4, and DB3-BOT-2, are listed as Cut with the reason Quantity increased, on the sheet where each was placed.

Deep dive

How CutPacket decides what goes back to the saw

Part IDs are the key. Each row in the parts CSV has an ID, such as B2-BOT, and that ID is the label on the piece. A part with a quantity above one gets a label for each piece, B2-STR-1 and B2-STR-2. When a revised CSV arrives, CutPacket matches parts by ID and ignores row order, so sorting or inserting rows in the spreadsheet changes nothing.

Tick what the shop has cut. On the Already cut tab, tick each piece that has been cut, or select a sheet and choose Mark sheet cut to tick every piece on it. The ticks are saved in the project file and carry into the revision, because the labels stay the same.

Import the revision. Choose Import revised parts CSV, or press Ctrl+R. The current list becomes the previous revision, the revision number goes up by one, and the Parts tab marks each part New, Changed, Qty up, Qty down, or Notes.

Five actions. After Generate packet, every piece gets one action. Cut is a new piece, a piece added by a higher quantity, or a changed piece not yet cut. Recut · scrap old is a changed piece that was already cut, shown with its old and new size. Cut as planned is unchanged and not yet cut. Keep is unchanged and already cut. Surplus is already cut but removed from the job or no longer needed after a lower quantity.

Kept pieces use no new stock. Pieces that are already cut and unchanged are left out of the new layout, so the sheets you pull for the revision carry only what still has to be cut. Their labels are already on them, so the revision prints none for them.

A name change is not a recut. When only a part’s name or notes change, the piece counts as unchanged, so a corrected description never sends good material back to the saw.

What the shop receives. The recut list PDF leads with Cut or recut now, then the surplus to set aside, the pieces to cut as planned, and the pieces already cut and kept. On the diagrams, pieces to cut or recut this revision are shaded blue, and the summary page states the revision work, such as 11 pieces to cut or recut, 7 already cut and kept, 5 surplus, with the sheets that need the saw.

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 Re-running a layout from scratch Marking up the old printout
Labels after the revision Same part IDs; pieces to cut tagged NEW, changed cut pieces tagged RECUT Pieces and sheets renumbered Corrected by hand
Pieces already cut and unchanged Kept, left out of the new layout, and not relabeled Laid out and labeled again Tracked from memory
Changed pieces Recut · scrap old, with the old and new size Mixed in with everything else Found by comparing lists by eye
Removed pieces Listed as surplus to set aside Left off the new list Crossed out by hand
Sheets that need the saw Named on the summary page, such as 1, 3, 4 Every sheet in the new plan Worked out by hand

FAQ

Straight answers—no glossary dump

What is a revision cut list?

It is the list a shop works from after a job changes partway through: which pieces are new, which already-cut pieces are now the wrong size and must be recut, which cut pieces are still good, and which are no longer needed. In CutPacket it is the Recut list tab and the recut list PDF and CSV in every exported packet, each line with its sheet and reason.

How does CutPacket know which pieces are already cut?

You tell it. Open the Already cut tab and tick each piece the shop has cut, or select a sheet in the layout review and choose Mark sheet cut to tick every piece on it. The ticks are saved in the .cutpacket project file. When you import the revised parts CSV, CutPacket checks each ticked label against the new list.

What happens when only a part’s name or notes change?

The piece is treated as unchanged. CutPacket compares size, material, grain, and quantity, and a change limited to the name or notes is marked Notes on the Parts tab. A piece already cut stays Keep, and a piece not yet cut stays Cut as planned, so a corrected description sends nothing back to the saw.

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

A label on every piece, in the order it comes off the saw. Cabinet cut list software built for the order that changes. A printed diagram for every sheet, with the cut order on the page.

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