CutOps Documentation | Practical Guide

Use this sequence on every job for predictable results and cleaner handoff.

1. 1

   Add parts. Enter dimensions and quantities for every piece you need to cut.

2. 2

   Set stock. Define the sheet sizes you actually have, with fixed or unlimited availability.

3. 3

   Apply constraints. Configure kerf (saw blade thickness), grain, orientation, and optimization depth to match floor reality.

4. 4

   Review and compare. Validate utilization, cut complexity, and any unplaced parts before release.

5. 5

   Export. Send PDF/PNG for visual handoff plus CSV/JSON for structured downstream use.

For the same effective inputs and settings, CutOps produces deterministic optimization output, which makes planning easier to review and repeat.

Define the job in the two main data areas before you run optimization.

Parts

Each part row should include length, width, and quantity. Add material tags and grain locks only where they are really needed.

Stock sheets

Stock rows describe available raw material. Use unlimited quantity only when it matches your planning scenario, otherwise enter fixed inventory counts.

Keep units, naming, and material labels consistent across rows. This is useful whether you are planning a full production batch or a one-off personal build.

These options have the biggest impact on result quality:

• Kerf / Saw blade thickness: material removed by the blade. Kerf should match your real blade width to avoid undersized parts and bad assumptions.
• Cut orientation: whether the solver should prefer width-first, length-first, or choose automatically.
• Grain direction: keeps orientation fixed when material appearance or structure matters.
• Stock mode: fixed quantities or unlimited stock assumptions.
• Optimization priority: least waste, least cuts, balanced, or throughput-oriented behavior.
• Optimization depth: fast, standard, or thorough search scope.
• Placement heuristic: the strategy used while placing parts on sheets.

Use all result views together before releasing the cut package.

The best plan is not always the one with the absolute lowest waste. In many real jobs, the better plan is the one that balances yield, cut simplicity, repeatability, and confidence on the floor or in the workshop.

Comparison mode is useful when one answer is not enough. Evaluate multiple candidates and rank them by material efficiency, production simplicity, or a balanced score.

This is valuable both for businesses protecting margin and for individual users trying to decide whether a plan is worth cutting with the material they already have.

1. Start with a balanced strategy as baseline.
2. Run a waste-focused variant and compare whether savings justify added cut complexity.
3. Run a simplicity-focused variant and compare handling time reduction versus extra material use.

Best practice: keep one visual export and one structured export so you can review the plan later or share it with the right person without losing context.

1. Confirm stock and part quantities before calculation.
2. Verify kerf (saw blade thickness) and orientation settings against real machine conditions.
3. Review unplaced items and decide whether to resize, split, or restock.
4. Spot-check first-sheet cuts before committing the full run.
5. Save or export the final cut package for traceability and reuse.

CutOps is designed around a local-first workflow. Core calculation happens in the browser, and many actions can be completed without sending job content to a server by default.

Depending on your account and plan, you may also use account-based features such as saving projects, workspace preferences, or cloud-backed continuity for your current work. If you rely on saved history, exports, or cross-device continuity, sign in before starting important jobs.

Project JSON export uses the same runtime schema used by the app import flow, so exported files can be re-imported without field remapping.

{
  "id": "proj_abc123",
  "name": "Kitchen Batch A",
  "createdAt": "2026-03-22T08:30:00.000Z",
  "updatedAt": "2026-03-22T08:45:00.000Z",
  "parts": [
    {
      "id": "part_1",
      "label": "Side Panel",
      "width": 600,
      "length": 720,
      "quantity": 2,
      "allowRotation": true,
      "enabled": true
    }
  ],
  "stockSheets": [
    {
      "id": "sheet_1",
      "width": 2440,
      "length": 1220,
      "quantity": 1,
      "enabled": true
    }
  ],
  "options": {
    "kerf": 3.2,
    "solverMode": "guillotine",
    "placementHeuristic": "auto",
    "optimizationPriority": "balanced",
    "stockMode": "fixed",
    "optimizationDepth": "standard",
    "roundingPrecisionMm": 0.1,
    "cutOrientation": "optimal",
    "labelsOnPanels": true,
    "useOnlyOneSheetFromStock": false,
    "considerMaterial": false,
    "considerGrainDirection": false
  },
  "patterns": [],
  "unallocatedPartIds": []
}

Verified behavior in the current codebase:

• Free-plan entitlement limits are set to 10 optimization runs per day and 300 panels per run; paid plans remove these limits.
• Compare Solutions and advanced optimization settings are gated behind paid entitlements.
• Optimization runs in a browser Web Worker with local in-thread fallback when worker creation is unavailable.
• Installed PWA scope is intentionally limited to /app routes.

For product and policy questions:

• Product support: Contact support
• Privacy: Privacy requests
• Accessibility: Accessibility help