1Upload the SVG files you want to work on; the file opens in an editable view in your browser with nothing installed.
2Make your changes — crop, rotate, resize, draw and recolour on an image; rewrite the words and restyle headings, lists and tables in a document — and every one of them lands on a working copy, never on your upload.
3Preview the result at full size before you commit to it.
4Export back to SVG, or to a format that re-compresses nothing if you are still part-way through editing.
SVG Editor FAQ
Anything specific to SVG in the editor?
+
Yes — nothing is sampled: the file is edited as text, so the result is still infinitely scalable and still diffable in version control. Worth knowing before you export over your only copy.
Is my file uploaded, or does editing happen locally?
+
Editing happens in your browser; the file goes to our workers only for the operations that genuinely need server-side processing, and it is deleted shortly afterwards.
How does SVG Editor let me edit without installing anything?
+
Concretely, the document is parsed into its shape tree rather than rasterised, so moving a path or retyping a label edits the object itself and the result is still resolution-independent afterwards. The editing surface is the browser, so there is nothing to install and no licence to hold.
What can I actually change?
+
Whatever the format itself can carry. On an image that is crop, rotate, flip, resize, drawing, text and shapes, filters and colour; in a document it is the wording, the headings, the lists and the tables. Everything is applied to a working copy, so the file you uploaded is never modified in place.
Does SVG Editor cost anything?
+
No. SVG Editor is free with no account and no watermark. Because SVG is text, nothing about your artwork is retained after the job — the uploaded file is deleted with everything else.
What can I upload to SVG Editor?
+
SVG files, including ones exported from Illustrator, Figma, Inkscape or a charting library. Embedded raster images inside the SVG are carried through as-is.
Is there a file size limit on SVG Editor?
+
Yes: free accounts process images up to 5 MB each, which an SVG essentially never approaches — a complex illustration is usually a few hundred kilobytes of text. In practice the thing that makes an SVG heavy is thousands of path nodes from an auto-trace, not the file size, and that is a different problem from the cap.
Will my SVG still be editable afterwards?
+
Yes. The output is still valid SVG markup — named layers, grouping and IDs survive — so you can reopen it in Inkscape or Illustrator and keep working. It also still diffs cleanly in version control.
Why does a MP3 site host SVG Editor?
+
MP3.to is built around the format that made portable audio ordinary: universally playable, small enough to ignore, and lossy in a way that only matters if you keep re-encoding it. Audio jobs cluster: the same person who needs a format changed usually needs the file cut, levelled or made smaller in the same sitting. Putting SVG Editor behind the same upload, the same caps and the same account is what turns three tabs into one.
What should I do with the result once SVG Editor is finished?
+
The converter on this site moves audio between MP3, WAV, FLAC, M4A, OGG and Opus, so the output format is a decision you can leave until the end rather than commit to at the start. Doing that after SVG Editor rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is SVG Editor here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build, the same workers, the same limits. What a MP3 site adds is a point of view about bitrates, about what survives an encode and about when a lossless intermediate is worth the upload time. It also starts from one fact about the format this site is named after: MP3 frames are fixed-size blocks, so a cut lands on a frame boundary and gapless playback markers do not survive a re-encode.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is listened to and nothing is indexed. Free accounts exist for history and batch size, not for access.
