xTool Studio 1.9 SVG import: what auto-merge changes before you run the job

xTool Studio 1.9 now automatically merges same-style objects when it imports a complex SVG or DXF. xTool says the change reduces object count and improves import, dragging and resizing performance. You can turn the behaviour off in Settings when you need to keep small objects individually selectable.

This is a file-preparation guide for the September 2026 software change, not a hands-on review of an xTool machine. We have checked xTool's current release notes and support documentation, but we have not tested Studio 1.9 against every xTool model or every kind of SVG. Always use the processing preview and frame the job before switching on a laser.

What changed in xTool Studio 1.9?

xTool's 11 September release notes name four related improvements for large or complex vectors:

• same-style objects in complex vector imports can be merged automatically to reduce object count;
• large SVG and DXF files should import faster;
• copying, dragging and resizing complex objects should be more responsive; and
• memory use and stability were improved for files that previously froze or crashed during repeated edits.

The release notes say auto-merge can be disabled in Settings. They do not say that every file is merged, publish a curve-count threshold, or promise that a formerly unopenable design will now work. Treat it as an import optimisation, not a repair for broken geometry.

What does “same-style” mean for a laser file?

xTool does not define the matching rule in the release note. Its layer documentation does explain that Studio uses vector-line colours to define layers, and that objects in the same layer share processing parameters. That makes colour a processing instruction, not decoration: one colour might engrave, another might score, and a third might cut.

The safe interpretation is therefore practical rather than technical: after an auto-merged import, confirm that objects meant to receive different processing settings still appear in different layers. Do not assume that two objects which look alike on the canvas will retain different power, speed or pass settings.

When should you leave auto-merge on?

Leave it on when the design contains many separate pieces that genuinely belong to the same processing layer and you will move or resize them as one composition. Typical examples include:

• a dense line engraving where every line receives the same setting;
• a traced silhouette made from hundreds of small islands that all cut from the same material;
• repeated decorative marks that will not be edited one by one; and
• a multi-colour file where each colour already maps cleanly to one intended process.

The benefit is editor performance. xTool's separate import troubleshooting page says SVG complexity depends on the number of curves rather than file size alone. A 200 KB vector can be harder to open than a 5 MB photograph because the vector asks Studio to manage many editable objects and curves.

When should you disable auto-merge?

Turn it off before import when individual selection is part of the next step. That includes jobs where you need to:

• delete or reposition one small piece without changing its neighbours;
• give two same-colour objects different processing settings;
• inspect overlaps and duplicate geometry object by object;
• change the processing order of individual pieces; or
• preserve a deliberately editable construction for later revisions.

If you are unsure, import a copy with auto-merge on, inspect the object list and preview, then re-import with it off if selection has become too coarse. Keep the source SVG or DXF unchanged. A Studio project should not be the only copy of customer artwork.

A safe SVG checklist for Studio 1.9

1. Keep process types on distinct colours. Use a small, deliberate palette so cut, score and engrave layers remain easy to recognise.
2. Convert live text to paths. xTool's SVG guidance says text elements should be converted to vector paths before import. Keep an editable text copy elsewhere because outlining is not reversible.
3. Remove hidden and off-canvas objects. Studio still has to parse geometry you cannot see.
4. Use real document dimensions. xTool Studio has an SVG DPI import setting, while DXF has unit controls. A file with explicit width, height and viewBox is easier to audit before it reaches the canvas.
5. Simplify only as far as the material allows. Extra nodes can slow the editor and produce tiny direction changes, but aggressive simplification rounds corners and erases detail.
6. Check for duplicate paths. Two coincident cut paths can send the laser over the same place twice even when the canvas looks normal.
7. Inspect the layer and object list. Confirm the expected layer colours, processing order and object access after import.
8. Preview, frame and test. Verify the work area, material placement and operation before starting the full job.

If you already have an SVG, the free SVG checker reads it locally and reports live text, embedded images, clipping, missing size, CSS styling and unusually heavy paths. It does not rewrite the customer's artwork. If your starting point is a PNG or JPG, the laser SVG and DXF converter makes a plain vector outline and lets you set the physical width before export.

Should you use SVG or DXF in xTool Studio 1.9?

xTool Studio supports both formats. Choose by what the file needs to preserve:

• Use SVG for filled shapes, colour-separated process layers and designs whose physical size is already stated in the file.
• Use DXF for line geometry from CAD or another workflow that already depends on DXF. Check Studio's DXF unit setting because unit interpretation is a separate import decision.
• Use a bitmap for a photographic engraving. Converting a photograph into thousands of vector fragments is usually heavier and less useful than importing a suitable PNG or JPG as an engraving image.

Makerfern exports SVG free. Pro adds DXF, including named colour layers, but Pro is not required merely because you own an xTool: Studio accepts SVG directly. Export DXF only when that format helps the actual workflow.

What if the file is still slow or will not open?

Work in this order so you do not erase useful detail prematurely:

1. Confirm you are on the current Studio version and importing a supported SVG or DXF.
2. Save a copy of the source file.
3. Export only the objects needed for this job instead of an entire design-board archive.
4. Remove embedded bitmaps, hidden elements and unused effects.
5. Reduce unnecessary trace specks and colours.
6. Simplify paths a little, then compare the result with the original at the finished physical size.
7. If the job is a filled engraving rather than a vector cut, consider a correctly sized bitmap instead.

xTool's support page says there is no strict image file-size limit and that computer performance affects the complexity Studio can handle. That is why “make the file smaller” is incomplete advice: reduce the curves and objects the job does not need, not just metadata or decimal places.

Sources and date checked

• xTool Studio Desktop V1.9 release notes, updated 11 September 2026; accessed 22 September 2026.
• xTool Support: file import failures in Studio, updated 7 May 2026; accessed 22 September 2026.
• xTool Support: import and parse vectors, updated 27 February 2026; accessed 22 September 2026.
• xTool Support: layer and object list, updated 20 May 2026; accessed 22 September 2026.

The useful change in Studio 1.9 is less waiting around a heavy vector. The useful habit has not changed: preserve intentional process layers, inspect what the importer produced, and test the job on the real material before committing the final piece.

Everything linked here is free to use, runs in your browser, and needs no account. If something in this post is wrong or out of date, it is worth telling us — the date at the top is the last time it was checked.