The short answer
An SVG file is a scalable vector image. Instead of storing a grid of pixels like a JPG or PNG, it stores instructions: draw a circle here, a line there, fill this shape with that color. Because it is math rather than pixels, an SVG stays perfectly sharp whether it is shown as a tiny favicon or blown up on a billboard.
That is why logos, icons, and simple illustrations are so often SVG. An SVG is also just text inside, so the file is usually small and can even be edited by hand.
How to open an SVG file
- A web browser. Drag the file into Chrome, Safari, Edge, or Firefox and it renders the image.
- Inkscape. A free, powerful vector editor for opening and editing SVG.
- Adobe Illustrator. The common paid option for working with vectors.
- A code editor. Open the SVG in VS Code or Notepad to see and tweak the underlying markup.
When SVG is the right choice
SVG shines for anything that needs to scale cleanly: brand logos, UI icons, charts, and flat illustrations. It is not meant for photographs. A photo has too much fine detail to describe with shapes, so stick with JPG, PNG, or WebP for those.
How to share an SVG file
Start with the part most pages skip: Snapy does not accept a bare .svg upload. The
box on the home page refuses it, on purpose. An SVG is not a picture as far as a browser
is concerned. It is a document that renders, and it can carry script, so hosting one at
its own public address is a phishing surface rather than an image share. That refusal is
deliberate and it is not going to change.
What does work, depending on what the other person needs:
- They need to see it. Export a PNG at the size they will view it and share that. Any editor does this, and a PNG opens in every browser on every device. Turn an image into a link covers that path.
- They need the editable file. Put the
.svgin a zip and upload the zip, or attach it to an email. It is a few kilobytes, so the attachment limits that break other files never apply to it. - It belongs to a page you are publishing. An SVG inside a zipped site is served normally, as part of that project, because it is then an asset of a page you uploaded rather than a page of its own. See hosting an HTML file.
Why an SVG is awkward to send at all
An SVG is tiny, which makes it sound like the easy case, and it is not. Some inboxes block the format outright, others render it as code rather than as a picture, and a few preview it correctly on a laptop and not at all on a phone. That inconsistency is the same property that makes it unsafe to host anonymously: an SVG is a small program, and every client decides for itself whether to run it.
So the rule of thumb is worth stating plainly. Send a PNG when the point is that somebody looks at the artwork. Send the SVG itself only to someone who is going to open it in an editor, and send it the boring way. For everything else, see how to share a file.
