1Upload the SVG files you want to work on; the file opens on an editable canvas in your browser with nothing installed.
2Crop, rotate, resize, draw, add text and shapes, or adjust colour — every change 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 lossless format instead if you are still part-way through editing.
SVG Editor FAQ
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.
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 anything lost when I export?
+
Only what the export format cannot represent. Choose a lossless output while you are still iterating and a compressed one when you are finished — exporting to a lossy format between edit sessions is what accumulates damage.
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 25 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 SVG Editor lower the quality of my SVG files?
+
No, and it cannot: an SVG has no pixel grid to degrade. The geometry is transformed mathematically, so the result is still crisp at any zoom level and still openable in a vector editor.
Can I run SVG Editor on several SVG files at once?
+
Yes. SVGs are small and parse quickly, so a batch of icons or logos finishes almost as fast as a single file. Settings apply uniformly across the set.
Why does a EPUB site host SVG Editor?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. SVG Editor runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once SVG Editor is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after SVG Editor means the conversion is made from the version you settled on, not from the one you were still fixing.
Is SVG Editor here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
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 read and nothing is indexed. Free accounts exist for history and batch size, not for access.
