LinkedIn Rejected My SVG Logo for the Fifteenth Time
I had just finished designing a company logo in Figma. Clean vector, perfect curves, scales to any size. Then I tried to upload it to LinkedIn — rejected. Twitter profile picture — rejected. Google Business profile — rejected. Instagram — rejected. Every platform I tried gave me some variation of "unsupported file type." SVG is code that browsers can interpret, but most social platforms and upload forms only want pixels. Converting to PNG at 1200×1200 solved every platform in one shot. Now I export from Figma once to SVG as the master, and render to PNG whenever I need to go anywhere that doesn't understand vectors.
Upload files
Files are processed on our server and deleted automatically when the job finishes. Nothing is stored or shared.
SVG is a program. PNG is a picture. Most of the world only accepts pictures.
Here's something most people don't realize about SVG: it isn't really an image file. It's a text file full of instructions — draw a circle here, fill it this color, place this curve here. When a browser or design tool opens an SVG, it executes those instructions and renders the result. That's why SVG scales to any size without going blurry. It's not stretching pixels; it's redrawing from scratch. The catch: most software in the world wasn't built to execute code when you upload an "image." Social platforms, HR portals, print labs, presentation tools — they expect pixels. PNG gives them pixels. That's the whole trade. You're not downgrading your logo; you're translating it into a language the destination understands.
The freelancer who sent a client a file they couldn't open
I did some logo work for a small restaurant a while back. Sent the final files as SVG — clean vectors, the proper way to deliver a logo. The owner emailed back two days later saying the file didn't open and asking if I could send "the logo as a normal image." I felt embarrassed. I knew SVG was the right format for a logo. He just needed to put it on a flyer in Word. He was not going to install Inkscape. He was not going to convert anything. He wanted to double-click a file and see his logo.
Now I deliver every logo job as a package: the SVG source for future designers, a 1200px PNG for general use, and a 512px PNG for small contexts like app icons and email signatures. Nobody has ever complained about getting too many files. Several clients have emailed back specifically to say they appreciated having multiple ready-to-use versions.
The sizes that actually cover every situation
After doing this for a few years I've stopped trying to guess the "right" size and just render a couple of standard sizes that cover everything I've ever been asked for:
- 1200 × 1200px: The one size that works everywhere — LinkedIn, Twitter/X, Facebook, Google Business profiles, most CMS media libraries. Start here.
- 512 × 512px: App icons, email signature logos, smaller profile contexts. Also the source size for generating favicons.
- 1920 × 1080px: Presentations, YouTube thumbnails, OG images for websites. The full-HD canvas covers most 16:9 uses.
- Print sizes (multiply by 300): If something needs to print at 4 inches wide, render at 1200px (4 × 300 DPI). I always add 20% margin just in case.
- Retina / HiDPI screens: If you're embedding a logo in CSS at 200px wide, render the PNG at 400px. The 2× ratio keeps it sharp on modern screens.
Why platforms really reject SVG — it's not just a pixel thing
There's a reason social platforms are aggressive about rejecting SVG even though modern browsers handle it fine. SVG can contain JavaScript. A malicious SVG uploaded to a profile picture could, in theory, execute code when other users view it. Facebook, LinkedIn, and Twitter learned this early — some of them through actual exploits — and they blacklisted SVG at the file validation layer. That decision got baked into every upload pipeline they've built since.
Beyond security, there's also the processing infrastructure: when you upload a photo, the platform generates 6 different resized versions for different contexts. That pipeline assumes it's receiving pixel data it can crop and scale. SVG doesn't fit that assumption. Raster-only pipelines are simpler, faster, and cheaper to run at scale — so they're not going away.
The font problem that ruined a logo render
A designer I know ran into this one and it cost him an afternoon. He'd made a wordmark logo in Figma using a custom font — nice brand-appropriate typeface, looked great in the browser. He exported the SVG and ran it through a converter. The output PNG had the name of the company in Times New Roman.
What happened: the SVG referenced the font by name in a text element. When the renderer tried to draw that text, it didn't have the font installed, so it fell back to whatever serif font was available. The shapes, colors, and everything else rendered correctly — just the lettering was completely wrong.
The fix is to convert all text to outlines before exporting from your design tool. In Figma: select the text layer, then Object → Outline Stroke (or Flatten). In Illustrator: Type → Create Outlines. This converts the letters to geometric paths with no font dependency. The SVG carries the actual shapes, not a font name, so it renders identically on any machine, in any converter, with no fallback substitution.
Brand files are deleted as soon as conversion finishes
SVG files are often the most sensitive asset a business has — the actual vector source of their logo, with all the colors and proportions and structural decisions that define the brand. I didn't want to build a tool that holds onto those. Your SVG and the generated PNG are both deleted from the server automatically as soon as the conversion completes. Processed over HTTPS, gone immediately after. No account, no storage, no upload history.
Frequently Asked Questions
The PNG looks slightly different from my SVG in the browser. Why?
SVG rendering isn't fully standardized — browsers, Illustrator, Inkscape, and server-side renderers all interpret the same file slightly differently, especially around filters, blend modes, and font hinting. If pixel-perfect accuracy matters, open your SVG in Chrome and visually compare the output. For most logos and icons, the difference won't be visible.
Does the PNG keep a transparent background?
Yes. If your SVG has no background rectangle or fill, the PNG will have a transparent background (alpha channel). It'll look like a checkerboard in image editors, and will sit cleanly on any background color in other software.
Can I render the SVG at a very large size for print or billboards?
Yes. That's the main advantage of starting from a vector — you can render a 10,000px PNG from a simple SVG logo and it'll be as sharp as a 100px version. Just enter the size you need. For print, the rule is: target size in inches × 300 DPI = pixel dimensions. A 10-inch print needs 3,000px minimum.
My SVG uses a Google Font or custom typeface. Will text render correctly?
Probably not, unless you convert text to paths first. External fonts aren't available to the server-side renderer and will fall back to a system font. In Figma: select the text, then Flatten. In Illustrator: Type → Create Outlines. Once text is paths, it renders identically everywhere.
Can I convert multiple SVG files at once?
Yes. Select multiple files and they'll all convert at the same output size. Download them individually or as a ZIP. Useful when you have a full icon set or multiple logo variants to export at once.
I need the same logo at five different sizes. Do I have to upload it five times?
Currently yes — one size per batch. Pick the largest size you need first (it's the one with the most uses), then re-upload for smaller sizes. SVG conversion is fast so it takes under a minute total. A multi-size export feature is something I've considered adding.
Other tools you might need
Resize image · Remove image background · Convert HEIC to JPG
Explore more free tools
Need a different format or workflow? These tools are part of the same Plomz toolkit and work the same way.