Files from DIYCutLab open at the wrong size
DIYCutLab SVGs state their size in millimetres (width="300mm"), so programs that read units import them at true size. When a program ignores the units, it guesses from pixels, and the result is off by a typical factor:
| Imported size is about… | Likely cause | Fix |
|---|---|---|
| 75 % or 133 % | 72 vs 96 pixels-per-inch assumption | Set the import DPI to 96 (or 72), or type the true width |
| 3.78× or 26 % | Millimetres read as pixels | Choose millimetres as the import unit |
| 25.4× or 4 % | Inches vs millimetres | Choose millimetres as the import unit |
Fix it
- Re-import with "fit to page" or "auto-size" turned off.
- Look up one part's width in
instructions/project-instructions.pdf(or the README). - Select the whole design in your software, lock the proportions and set the width to the sheet or part width listed. Everything scales together, so one dimension fixes all.
- Measure again before cutting.
SVGs you import into DIYCutLab
Many SVGs from drawing programs or the web have no physical units, only pixels. The import report then says the scale is unknown and asks for the real overall width. Measure the object you are copying, type that width, and choose Set scale.
Why pixels are ambiguous
The SVG standard defines 96 px per inch, but some programs export at 72 px per inch and some cutters assume either. Only absolute units (mm, cm, in) or a viewBox with absolute width and height are reliable, which is why DIYCutLab always writes both.