Contents
  1. The short answer
  2. Ways to preview the rendered logo
  3. Choosing a method by situation
  4. What the preview does not prove
  5. A note on reuse
  6. Evidence gaps

The short answer

An SVG file is text: XML markup that describes shapes, paths, colors and sometimes embedded images. Visual Studio Code therefore opens an SVG logo as source code, which is useful for inspecting how the logo is built but does not show what it looks like. To see the rendered logo, use a preview. You can reopen the file in an image or preview editor, or install a preview extension from the Extensions view. Which built-in option you have depends on your VS Code version, and no version-specific evidence was supplied for this guide, so check the options in your own installation.

In this guide, "viewing" a logo means two separate things: reading its markup and seeing its rendered artwork. Each tells you something the other cannot, so a careful review of a logo file uses both.

  • Reopen with a different editor: with the SVG open, run the command "Reopen Editor With…" from the Command Palette and choose an image or preview editor if your version lists one. This replaces the code view with the rendered image.
  • Preview to the side: some setups and extensions add a preview button to the editor title bar. A side-by-side preview lets you edit the markup and see the result without switching tabs.
  • Preview extension: search the Extensions view for "SVG preview" if no built-in preview is available. Compare the extensions' descriptions, update history and permissions before you install one, because the features vary.
  • Outside the editor: opening the file in a web browser gives a second rendering to compare against. This helps when you suspect that a preview tool is displaying something incorrectly.

Choosing a method by situation

Situation | Suggested approach
You only need to confirm what the logo looks like | Reopen the file in an image or preview editor
You are editing colors, paths or the viewBox | Use a side-by-side preview so the changes are visible as you type
Your VS Code version has no built-in SVG preview | Install a preview extension
The rendering looks wrong or inconsistent | Compare it with a web browser before you change the file

What the preview does not prove

A clean preview shows that the file renders. It does not show that the logo is true vector artwork. The .svg extension is not enough evidence either, because an SVG can wrap a bitmap image. Such a logo will blur or pixelate when it is enlarged, even though the file name looks correct. Open the code view and look for an image element that points to embedded raster data.

<!-- Vector shape: scales cleanly -->
<path d="M10 10 H 90 V 90 H 10 Z" fill="#1a1a1a"/>

<!-- Embedded bitmap: an SVG wrapper around a raster image -->
<image href="data:image/png;base64,..." width="100" height="100"/>
  • Raster images: an image element with base64 data or a reference to a PNG or JPEG means part or all of the logo is not vector artwork.
  • Live text: a text element depends on fonts installed on the viewing machine, so the wordmark may render differently on other computers. Delivered logo files usually have the lettering converted to outlines (paths).
  • viewBox and dimensions: the viewBox attribute sets the drawing area. A missing or mismatched viewBox can crop the logo or add unexpected padding when it is placed in a layout.
  • Background: a preview may show the logo against a checkerboard or against your editor theme. Look for a full-size rectangle near the start of the file to tell whether the background is transparent or part of the artwork.
  • Colors: fill and stroke values in the markup show the exact colors the file specifies. Compare them with the brand's documented palette, if you have one, rather than judging by eye in the preview.

A note on reuse

Being able to open and preview a logo file does not mean you have permission to use it. Rights to a logo come from its owner and any brand guidelines or license they provide, not from the file being available to you.

Evidence gaps

No confirmed details were supplied about specific VS Code releases, menu labels, default behavior or named extensions. The steps above describe general approaches. Confirm the exact commands and options in your installed version.