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

Sheet layouts with the kerf,the trim, and the grain built in.

Set the blade kerf and edge trim once, mark which parts follow the grain, and CutPacket packs each board with straight rips and crosscuts in numbered order. Every run tries a range of layout strategies and keeps the plan that places the most pieces on the fewest sheets.

If your parts are rectangles cut on a panel saw or table saw, CutPacket lays out guillotine cuts with your kerf, trim, and grain, and prints the sequence.

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

Graph paper and a calculator are slow, and they forget the kerf.

Laying out boards by hand means sketching each 2440 by 1220 panel, fitting the big carcass parts first, and squeezing stretchers into whatever space is left. The blade takes about 3 mm on every pass, the factory edge needs trimming, and a few millimetres missed per part add up to one that no longer fits at the end of a rip.

Where tooling usually breaks

A layout you cannot saw is only a drawing.

Some layout tools nest parts like a jigsaw, tucking pieces into L-shaped gaps that a panel saw cannot reach without a plunge. Others treat grain as optional, so a tall side comes out with its figure running across instead of up. And a result that shifts on every run means the printed pages in the shop stop matching the screen.

Where CutPacket lands

Straight cuts, grain honored, same answer every time.

CutPacket builds guillotine layouts, where every cut runs edge to edge across the piece being cut, and lists those cuts in order with their positions. Parts marked length or width keep the grain on grained stock. The search is deterministic, so identical parts, stock, and settings produce an identical layout and identical labels on every run.

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

An imperial shop with fractions in the list

A shop works in inches. The parts list has sizes like 23 1/4 and 34 1/2, the blade takes 1/8 inch, and the factory edges of each 48 by 96 inch sheet need a half-inch trim.

The owner sets Unit to in, or adds a unit column, and the CSV imports as written: CutPacket reads mixed numbers such as 23 1/4, takes kerf and trim as 1/8 and 1/2, and prints diagrams, labels, and the cut list CSV in inches.

Two sheet sizes of the same material

The rack holds full sheets and a few cut-down sheets of the same white melamine, and the owner wants the large parts on full sheets and the smaller sheets used where parts fit.

Both sizes go in the stock CSV with their quantities. CutPacket opens the largest sheets first, fills the smaller ones with parts that fit, never uses more sheets than the stock list says are on hand, and names any piece that needs another sheet.

A sheet that is already on the saw

The operator has sheet 1 clamped and marked up and wants it to stay exactly as printed while the rest of the plan is generated again.

Select the sheet and choose Pin. On the next Generate packet, that sheet keeps its exact layout, the other sheets are laid out around it, and the summary page marks it pinned.

Deep dive

How CutPacket lays out a sheet

Trim first. The edge trim is taken off every side of the sheet before any part is placed, so a 10 mm trim on a 2440 × 1220 sheet leaves 2420 × 1200 to work with. On the diagram the trim band is shaded, and the first two cuts in the sequence are the reference rip and crosscut that clean the edges.

Kerf between pieces. The blade kerf, 3.2 mm unless you change it, is taken out wherever a part is followed by more material. Each cut in the sequence gives its position and its span, measured from the bottom-left corner of the sheet, in the job’s unit.

Guillotine layouts. Every layout is built as a cut tree: a cut splits a panel into two rectangles, and each of those is split again. Every cut therefore runs edge to edge across the panel in front of the operator, with no plunge cuts or stopped cuts. The diagram lists them as rips, along the sheet length, and crosscuts, across it.

Grain rules. Stock sheets are marked grain yes or no. On grained stock, a part marked length keeps its length along the sheet length, a part marked width is turned 90 degrees, and a part marked none can go either way. On stock marked no, such as melamine or MDF, every part can rotate. A part with blank grain on grained stock is flagged before layout, so grain is decided by you.

Several strategies, one plan. Each run tries a set of sort orders, placement rules, and split rules, and keeps the plan that places the most pieces on the fewest sheets, then the one that leaves one sheet as empty as possible for a reusable remainder. Because the search is deterministic, running it again with the same inputs gives the same layout and the same labels.

Materials and sheet sizes. Parts are matched to stock by material name, ignoring letter case and extra spaces. Within a material the largest sheets are used first, and the stock quantity is respected. A piece that needs more stock than the list holds is named in a message and on the summary page, so you can add a sheet and generate again.

Offcuts worth keeping. Leftover areas at least 100 mm on both sides are hatched and labeled with their size on the diagram, and the sheet summary in the app names the largest one.

Yield on every sheet. Each sheet shows its piece count and yield, and the summary page gives the overall yield and the number of sheets per material, so you know how many to pull before the first cut.

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 Online optimizer Spreadsheet by hand
Cuts a panel saw can follow Guillotine layouts, with the rip and crosscut order printed Varies by site Depends on the sketch
Kerf and edge trim Set per job in mm or inches, fractions such as 1/8 accepted Usually a kerf field Added by hand
Grain direction Length, width, or none per part; yes or no per sheet Varies by site Remembered by whoever draws it
Same layout on every run Yes, deterministic for the same inputs Varies by site One sketch per job
Where the job data goes Stays on this PC. Nothing uploads. Uploaded to the site Stays on this PC

FAQ

Straight answers—no glossary dump

How does a cut list optimizer handle saw kerf?

It takes the blade width out between neighbouring parts, so the parts along a rip still fit once the saw has cut. In CutPacket, type the kerf under Saw, such as 3.2 mm or 1/8 in, along with the edge trim, and choose Apply saw settings. Generate again and every layout, diagram, and cut position uses the new values.

What is a guillotine layout?

A layout in which every cut runs straight from one edge of the panel to the other, the way a panel saw or table saw cuts. Each cut leaves two rectangles, and each of those is cut again. CutPacket produces guillotine layouts and prints the rips and crosscuts for each sheet in the order the operator makes them, with their positions.

Does it work in inches and millimetres?

Yes. Choose mm or in under Saw, or let the CSV say: CutPacket reads a unit column, a unit in the header such as length_mm or width_in, or a suffix on the value such as 610mm or 24". Fractions and mixed numbers such as 3/4 and 23 1/4 are read too, and every diagram, label, and CSV prints in the job’s unit.

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 printed diagram for every sheet, with the cut order on the page. Cabinet cut list software built for the order that changes. The order changed. Here is what goes back to the saw.

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