1Upload your SVG files and wait for the preview to appear.
2Drag out the region you want to keep, or lock the selection to 1:1, 4:3 or 16:9 and drag freely inside that ratio.
3Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4Download the cropped SVG file, with everything outside the frame discarded.
Crop SVG FAQ
Does my source format change how a crop behaves?
+
It can. SVG is XML geometry rather than pixels, so it scales to any size without blurring but has no pixel grid to sample from. That decides whether the crop is a pure pixel operation or whether the file has to be rebuilt around it.
Anything specific to SVG worth knowing before I crop?
+
Yes — nothing is sampled: the file is edited as text, so the result is still infinitely scalable and still diffable in version control. That is the sort of detail that only shows up after you have overwritten the original.
What is the most common mistake when cropping SVG files?
+
Cropping before resizing. Crop first from the full-resolution original, then resize the result — doing it the other way round means the region you keep has already lost detail it did not need to lose.
How does Crop SVG select and cut the area?
+
Concretely, cropping an SVG means rewriting the viewBox rather than discarding geometry, so shapes outside the new frame are clipped in the view but the artwork itself stays intact and recoverable. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
Can I run Crop SVG 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.
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.
Is there a file size limit on Crop SVG?
+
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 Crop SVG 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.
Why does a Word site host Crop SVG?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. Crop SVG shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once Crop SVG is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is Crop SVG here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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.
