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 printed diagram for every sheet,with the cut order on the page.

Each sheet in the job gets its own landscape page: a to-scale drawing, each panel marked with its ID and dimensions, an arrow for the veneer direction, hatched offcuts with measurements, and a sequenced table of cuts beside the drawing.

For panel saw and table saw work, CutPacket prints one US Letter page per sheet with the layout, the saw order, and every cut position.

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

A layout on a screen does not help at the saw.

The operator at a panel saw needs the sheet in front of them on paper: which strip to rip first, where each crosscut falls, and what each part is once it falls away. A phone photo of a monitor or a sketch on cardboard leaves out the sequence and the veneer direction, and it seldom lasts a day in the shop.

Where tooling usually breaks

The wrong first cut ruins the rest of the sheet.

On veneered ply, order matters. Crosscut too early and a long strip is lost; rip in the wrong direction and a tall side loses its vertical figure. Usable leftovers that could have become small shelves get tossed because their dimensions were never written down.

Where CutPacket lands

A page per sheet, built for the shop printer.

CutPacket draws each sheet mostly in black on white so it prints cleanly on an ordinary office printer. Pieces show their ID and size and a number for the order they come off the saw. A cut sequence table lists each rip and crosscut with its position and span, grained stock gets a grain arrow, and offcuts of 100 mm or more each way are hatched and sized.

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 panel saw operator working alone

The operator cuts every sheet for a kitchen and wants to work from a page clipped to the saw rather than walk back to the office computer between sheets.

The cut diagrams PDF has a summary page and one landscape page per sheet. The operator follows the numbered cut sequence, from the reference rip and crosscut that clean the factory edges to the last crosscut, and checks each piece against its saw number.

Pulling the right sheets from the rack

Before cutting starts, the shop needs to know how many sheets of each material to pull and which sheets have work on them this revision.

The summary page lists sheets per material, such as Maple ply 18mm: 2 sheets and White melamine 18mm: 3 sheets, and a table with each sheet’s stock, size, piece count, yield, and status, so the rack is visited once.

Keeping the good offcuts

The shop keeps reusable offcuts for fillers and small parts but has no record of their sizes until someone pulls out a tape and measures them.

Every leftover at least 100 mm each way is hatched on the diagram with its size, such as offcut 1452.8 × 410.4, and the layout review in the app names the largest offcut on each sheet.

Deep dive

How to read a CutPacket cutting diagram

Orientation. The sheet is drawn the way it sits on the saw: X runs along the sheet length from the bottom-left corner, and Y runs across its width. A grained sheet has a grain arrow under it, pointing along the length.

Trim band. A light band around the edge shows the edge trim. The first two cuts in the sequence, a rip and a crosscut at the trim distance, square the sheet before any part comes off.

Pieces. Each piece shows its label in bold and its size, length × width as listed in the CSV, even when the piece was turned to fit. The small #n in the corner is the order the piece comes off the saw. In a revision, pieces to cut or recut are shaded blue, and the legend under the diagram says so.

Cut sequence. The table beside the diagram numbers every cut. Each row says Rip or Crosscut, where it falls, such as Y = 110 or X = 974, and its span, such as 10 → 2430, all in the job’s unit. The cut list CSV in the same packet holds every cut of every sheet with the sheet number, stock ID, material, order, type, axis, position, and span.

Offcuts. Hatched areas are leftovers at least 100 mm each way, labeled with their size so they can be marked and racked for the next job.

Header and footer. Every page carries the job name, the revision, and the revision note at the top, and the date and time it was generated, the kerf, the edge trim, and the unit at the bottom, so a printed page always shows which job and settings it belongs to.

Summary first. Page one lists the sheet count, the piece count, the overall yield, and the sheets per material. In a revision it adds the pieces to cut or recut, the pieces kept, the surplus, and the sheets that need the saw, with a table giving each sheet’s status: needs saw, cut as planned, or pinned.

Built to print. Pages are US Letter, landscape for the sheets and portrait for the summary, with the fonts embedded so the PDF looks the same on any PC that opens it.

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 is on each page of the cutting diagram?

One sheet per landscape page: the layout drawn to scale with each piece’s label, size, and saw number, the trim band, hatched offcuts with their sizes, and a grain arrow on grained stock. Beside it, a cut sequence table numbers every rip and crosscut with its position and span. The header names the job and revision, and the footer gives the kerf, trim, and unit.

Can I get the cuts as a spreadsheet as well?

Yes. Every exported packet includes a cut list CSV with one row per cut: the sheet number, stock ID, material, cut order, rip or crosscut, axis, position, and span, in the job’s unit. It is UTF-8 so Excel opens it cleanly. The packet also holds a labels CSV, a recut list CSV, and the plan as JSON.

What paper does the cutting diagram print on?

US Letter. The summary page is portrait, and each sheet gets a landscape page so the layout prints as large as the page allows. The diagrams are drawn mostly in black on white for an ordinary office or shop printer, and the fonts are embedded in the PDF, so it prints the same from any PC.

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