Does my SVG have an embedded image?
An SVG is a container. It can hold true paths, or it can hold a JPEG wrapped in a vector envelope. Both open in a browser and look identical. Only one survives a cutter, a stitcher or a printer.
The tell is in the source. Look for an image element, a base64 data block, or a filter that turns paths into pixels. If any of those are present, some or all of the artwork is a bitmap, and the 'vector' claim is only about the file extension.
That matters because production tools do not all fail the same way. A printer may rasterise the whole page at 300 dpi and get away with it. A vinyl cutter has no idea what to do with a photograph. An embroiderer cannot stitch pixels.
Three ways to check
- Open the SVG in a text editor and search for image, base64, or data:image. Any hit means a bitmap is inside.
- Search for filter and feGaussianBlur. A blur is not necessarily a bitmap, but it often signals an effect that will not survive a cut.
- Search for text and tspan. Live text is not a bitmap, but it is also not outlined, so it will reflow or fall back to a different font on another machine.
The free checker on this site does the same checks in the browser and reports the path count, path commands and the canvas size. Nothing is uploaded.
Why a bitmap in an SVG is a problem
- It has a fixed resolution. Enlarging it for a sign reveals pixels that were always there.
- It cannot be cut. A cutter follows paths; a bitmap has none.
- It cannot be stitched. A digitiser would have to redraw it first, which is the work you thought you had avoided.
- It cannot be recoloured cleanly. Changing the brand colour means editing the bitmap, not the shape.
- It often carries a background. A white box behind a logo becomes a white box on a coloured garment.
What to do about it
| What you found | The fix |
|---|---|
| image or base64 in the SVG | Re-export from the original vector source, or redraw; re-saving the SVG will not remove it |
| Live text | Outline the type in the design tool, then re-export |
| Thousands of path commands | Clean up the trace or redraw; the file is technically vector but not production-grade |
| Filters and gradients | Flatten to solid shapes for cut and embroidery versions |
Worked example: the logo that was a PNG
The brief
A contractor downloads an SVG from a logo builder. The browser shows a crisp mark. The sign shop opens it and finds a 512 px PNG inside the SVG.
The canvas is 512 × 512, so scaling to a 1.2 m van panel means roughly 2.4 times the pixels across. At that size the edges are visibly soft, and the cutter has nothing to follow. The shop quotes a redraw, which is the cost the 'vector' download was supposed to avoid.
The production fix is to rebuild the mark as geometry: a small number of closed paths, solid colours and outlined type. That is also the moment to make the one-colour and reverse versions the production chain will ask for.
What our pack ships
Every lockup is authored as geometry and exported as SVG and PDF with no embedded raster and no live text. The same spec also produces the one-ink versions a cutter and a screen printer work from, so the vector claim holds all the way to the machine - the separation itself stays where it belongs, with the printer.
Questions
Can I just re-save the SVG to remove the embedded image?
No. Re-saving keeps whatever objects are inside. If an image element or a base64 block is present, it has to be replaced with paths, which means going back to the original vector source or redrawing.
Is an SVG with live text still vector?
Technically yes, but it is not production-ready. The text depends on a font being installed, so it can reflow or substitute on another machine. Outline the type before sending it to a printer or cutter.
How many paths is too many?
There is no hard limit, but a simple two-colour mark should be in the hundreds of path commands, not the tens of thousands. High counts usually mean an auto-trace and predict a lumpy cut.
If the file is the problem, the pack is the fix.
The Production Pack is $149, one time: true vector masters, six lockups, a print PDF and EPS, one ink per file and unlimited parametric edits.
See the production pack Audit my current file
Free tools: vector check · 12-file audit · 16px legibility · CMYK shift · stitch estimate
For agents
The same pack is available to a machine: a structured brief, a JSON manifest, x402 in USDC on Base, and an MCP tool contract.
Agent access · OpenAPI · llms.txt · MCP
Agent API: the contract, the free endpoints and the paid x402 checkout are live. USDC on Base, no account, no API key.
Related guides
- Vectorize a logo without inheriting the mess
Auto-trace turns pixels into paths, not into a design. How to tell a clean vectorisation from a traced bitmap, and when redrawing is the cheaper answer.
- Logo file fix: the twelve files a real business needs
Most logo downloads are missing the files print, signage and embroidery ask for. A practical audit of the twelve deliverables, and how to check yours.
- Logo for vinyl cutting and signage: closed paths and minimum strokes
A vinyl cutter follows the path, so every open path, hairline and floating island becomes a problem. What a cut-ready logo needs, and how to test it.