Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

SVG Editor

Free Online SVG Editor

Go with your files

*Files deleted after 24 hours

Optimize up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Edit SVG Online

1 Upload the SVG files you want to work on; the file opens on an editable canvas in your browser with nothing installed.
2 Crop, rotate, resize, draw, add text and shapes, or adjust colour — every change lands on a working copy, never on your upload.
3 Preview the result at full size before you commit to it.
4 Export back to SVG, or to a lossless format instead if you are still part-way through editing.

SVG Editor FAQ

Does the file format limit what the editor can do?
+
It does. SVG is XML geometry rather than pixels, so it scales to any size without blurring but has no pixel grid to sample from. What the format can represent bounds what any editor can preserve, here or on the desktop.
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.
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.
Crop, rotate, flip, resize, draw, add text and shapes, and apply filters and colour adjustments. Everything is applied to a working copy, so the file you uploaded is never modified in place.
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.
SVG files, including ones exported from Illustrator, Figma, Inkscape or a charting library. Embedded raster images inside the SVG are carried through as-is.
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.
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.
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. SVG Editor is on the same upload and the same account so those questions get answered in one place.
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.

Rate this optimizer
5.0/5 - 0 votes
ns6.com — Buy your domain from $2/year. Online in minutes.
Or position your files here