Setting Converter
Found a setting for a 40W machine but yours is 60W? Enter the original and your wattage and get three graded starting points — balanced, faster, or cooler — based on matching the energy delivered per pass rather than scaling the numbers blindly.
Setting Converter
Take a setting made for one laser and estimate a starting point for another wattage of the same laser type. Cross-type (diode ↔ CO2 ↔ fiber) isn’t converted — the wavelengths behave too differently.
The setting you have
Your machine
Pick a brand + model to auto-fill laser type and wattage, or set them by hand.
Estimated starting points — 70W → 50W CO2
Power scaled to match energy at the same speed.
Same power means a weaker laser must slow down.
Lower power, slower pass — less heat and charring on delicate materials.
These are math-based starting points (matched energy per pass), not guaranteed settings. Always test on scrap — real results depend on material, focus, lens, and air assist. For cutting, favor the faster option; for dark engraving on wood/MDF you may need to stay slower.
Which of the three to pick
Balanced holds the speed and adjusts power — the safest general starting point. Faster keeps the power and raises the speed, which is usually what you want when cutting on a stronger laser, since it gets you the throughput the extra wattage was for. Cooler lowers power and slows down, for heat-sensitive materials where scorching matters more than speed.
Why it refuses to convert between laser types
Diode, CO2 and fiber lasers interact with material through genuinely different physics — a wavelength that engraves anodised aluminium beautifully may not mark bare wood at all. There is no honest multiplier between them, so the converter declines rather than handing you a confident wrong number. For a different laser type, search the library for a setting made on that type.
It is a starting point
Two machines of the same model and wattage still differ — tube age, lens condition, focus, ambient temperature and air assist all move the result. Treat the output as the first square of a test grid, not a final answer, and always run it on scrap.