PerfectVector
By Irene Kim10 min read

Xara Bitmap Tracer: Tune the Trace and Inspect the Shapes

Use Xara Bitmap Tracer modes and controls to turn a bitmap into editable shapes. Check curves, corners, color regions, and exported artwork before delivery.

On this page

Xara's Bitmap Tracer converts a bitmap into editable vector shapes. Select the source bitmap, open the tracer, choose a mode that suits the artwork, run Trace, and use Insert to place the result in your document. Then test the shapes: can you select the intended region, change its color, and adjust an edge without rebuilding the artwork?

For a flat logo or symbol, start with a simple trace. More colors, passes, and control points can preserve shading, but they can also make a small illustration harder to edit. The useful result is the one that supports your next change.

Open the tracer with the correct bitmap selected

Import your source into a working Xara document and select it. Xara's tracer documentation says the selected bitmap becomes the initial source; without one, the dialog can show a default bitmap instead. Check the source preview and bitmap name before adjusting anything.

The documentation labels the menu route Utilities → Bitmap editor, while older Xara tutorials call it Bitmap Tracer. A documented alternative is the Trace button in the Bitmap Gallery. Use the tracer command available in your desktop edition and confirm that its dialog shows the original bitmap, output preview, and trace mode. These instructions follow Xara's published desktop help; the example below is a separate SVG conversion, not a native Xara session.

Keep the original bitmap on the page for comparison. Run Trace to calculate the preview, change one setting, and trace again. When the result is worth inspecting as objects, choose Insert. Move the inserted result beside the bitmap so an underlying image cannot disguise missing regions.

Choose a trace mode before changing the sliders

Xara documents four modes. Their color counts are upper limits, not a promise that the result will contain that many useful objects.

Source and goalStarting modeWhat to inspect
Black-and-white mark with solid areasMonochrome, limited to two colorsSmall gaps, background shapes, and the silhouette
Grayscale drawing where gray shading mattersGrayscale, up to 256 gray levelsWhether faint shading is useful or just capture noise
Flat illustration with several colors256 colorExtra edge shades and whether intended regions remain separate
Photograph where tonal variation is essentialPhotographic, up to 24-bit colorShape complexity and whether the result is practical to edit

The default photographic mode attempts to reproduce a picture with many colored shapes. That is often unnecessary for an emblem consisting of three flat colors. Choose the mode for the intended artwork, rather than keeping the default because the input happens to be a PNG or JPEG.

Before tracing, crop unrelated surroundings and use a source where essential edges are visible. A larger copy of the same blurry image does not supply a missing corner. For precise lettering or geometric logos, rebuilding a few known shapes may take less work than correcting an uncertain automatic trace.

Tune detail, color, and edges separately

The controls solve different problems. Xara's official explanation of tracer settings is especially useful for distinguishing curve accuracy from corner smoothing.

Passes and color tolerance

Passes ranges from one to five. Additional passes try to match shading more closely and increase the resulting file's complexity. For broad areas of flat color, one pass is a sensible starting point. Add passes when the missing shading matters to the final design.

Color tolerance determines how much colors must differ before the tracer treats them as separate areas. Increasing tolerance accepts a larger difference within an area; reducing it can preserve finer color differences. Judge the result at boundaries you actually need to edit, such as the join between a colored tail and body.

For multiple passes, the documented initial tolerance should be higher than the final tolerance. For a single pass, only final color tolerance has an effect. Changing the initial value while using one pass is therefore an unhelpful way to troubleshoot a result that stays the same.

Remove noise and minimum area

Remove noise suppresses small unwanted color areas, including dust or dithering. Minimum area ignores regions below a size measured in pixels. Both can remove details you intended to keep.

Use a small identifying feature as a checkpoint: an eye, a punctuation mark, or a narrow gap. If it disappears after a setting change, undo that change before making another. Do not judge noise removal only by whether the preview looks cleaner overall.

Accuracy and smoothing

Accuracy controls how closely smooth outlines are followed. Higher accuracy can require more control handles. The manual explicitly says this control does not affect corners.

Smoothing controls the treatment of sharp changes in direction. Inspect pointed tips and notches after changing it. A rounded corner and a wobbly curve call for different checks; moving both controls together makes it harder to tell which change helped.

Keep one acceptable trace as a reference and produce a second version for the next experiment. Compare the same small area in both, then inspect at the intended display or print size. Stop increasing detail when it adds editing work without preserving anything the design needs.

Test one color change before accepting the trace

A practical editability test is simple: change the fill of one intended region and confirm that the rest stays intact. We used an original, prepared three-color fish image to demonstrate that test with an actual PerfectVector conversion.

The unmodified SVG contained four closed paths and four fills: a teal body, a navy eye, an ochre tail, and a near-white full-canvas background. It contained no embedded images and no SVG groups. In this particular output, the tail was one path. We made a separate working copy and changed only its fill from #d59d2b to #c85665; all contour coordinates, other fills, and the background stayed unchanged.

Test the edit you need
Prepared fish bitmap, actual four-path SVG output, and a working SVG copy with only the tail recolored with blue SVG path outlines
An original synthetic source and actual PerfectVector SVG output. The third panel is an explicitly edited SVG copy: one tail fill changed, with geometry and background preserved. This is not a Xara trace, import test, or product screenshot. Blue lines overlay the actual SVG paths for inspection; background outlines are omitted.

This proves that the tail can be recolored independently in the inspected SVG. It does not prove that every traced color becomes one object, or that a destination editor will preserve the same object structure. Use the same operation on your inserted Xara result and check what is actually selected.

If Xara selects a group, you may not need to dismantle it. The editing-inside-groups guide documents Ctrl+click with the Selector tool to select an object inside a group. You can also open group contents in a separate view. Check the selected region, change its fill, and inspect nearby edges before continuing.

Test the background separately. A white page can hide a white background shape. In our SVG, the background is an actual full-canvas path, so the output is not transparent. Remove a background only after identifying it, then inspect the artwork over a contrasting color. Do not delete every white shape if the design uses white details.

When to use a separate SVG conversion

If the source is a raster image and you want an SVG to inspect before bringing it into your design document, use PerfectVector's image-to-vector converter. Download the SVG, test its paths and color regions, and then import it into your target editor. The fish example above shows the scope of that route: real editable geometry plus a specific, verified fill change.

Xara's current supported-format table lists SVG for import and export. Check your edition's available formats and test the imported file on a spare page. Do not run Bitmap Tracer again on an SVG that already contains the vector shapes you want.

Use Xara's native tracer when its controls give you the result you need within the document you are already editing. Use an external conversion when obtaining an SVG first fits your workflow. We have not traced this fish in Xara, so these examples cannot establish which tool produces a better trace.

If you are choosing between approaches, the image tracing and AI vectorization guide explains the distinction. For a fair comparison, give both tools the same source and test the same edits.

Inspect the exported artwork as well

Save the editable Xara document before exporting. Xara's import and export guidance distinguishes the .xar master from exchange formats and explains that unsupported features can require conversion during export.

Open the exported file in its intended destination. Check the silhouette, important corners, colors, and any transparent areas. Try the one-region edit again if another designer needs editable artwork. A correct appearance in the Xara document is only part of the delivery check.

For a repeatable review, use the vector trace quality scorecard. Record a concrete defect such as “the tail selects with the background” or “the eye disappears at the delivery size.” That makes the next correction much easier to choose than a general request for a cleaner trace.

FAQ

Where is Bitmap Tracer in Xara? Xara's desktop tracer help labels the Utilities route as Bitmap editor, while older tutorials call it Bitmap Tracer. The help also documents a Trace button in the Bitmap Gallery. Select your bitmap and confirm that the tracer shows the correct source before running it.

Why does changing initial color tolerance do nothing? On a single pass, Xara uses only final color tolerance. Initial tolerance applies to multiple passes, where the documented initial value should be higher than the final value.

Should I maximize accuracy for every image? No. Higher accuracy follows smooth outlines more closely but can add control handles. It does not control corners. Increase it only when the curve improvement matters, and inspect corners separately when adjusting smoothing.

Can I import an SVG instead of tracing a bitmap? Xara's current format table lists SVG import. Test your edition and file on a spare page, then inspect the imported shapes. An SVG that already contains usable paths does not need another bitmap trace.

Sources

  1. Xara: Tracer — source selection, modes, passes, tolerance, noise, accuracy, and smoothing.
  2. Xara: Editing inside groups — selecting and editing individual objects within a group.
  3. Xara: Import and Export Supported File Formats — the current documented SVG import and export entries.
  4. Xara: General notes on exporting and importing — preserving the master document and testing exchanged files.

Need an SVG starting point? Convert your image to vector, inspect one meaningful color change, and test the file in your destination editor before delivery.

More from the blog

Turn your image into
clean, editable vector paths