Monthly Downloads: 0
Programming language: TypeScript
License: MIT License
Tags: Miscellaneous     Code Design     React     React-component     Component     Svg    
Latest version: v2.2.0

react-inlinesvg alternatives and similar libraries

Based on the "Miscellaneous" category.
Alternatively, view react-inlinesvg alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of react-inlinesvg or a related project?

Add another 'Miscellaneous' Library



NPM version CI Maintainability Test Coverage

Load inline, local or remote SVGs in your React components.

View the demo


  • 🏖 Easy to use: Just set the src
  • 🛠 Flexible: Personalize the options to fit your needs
  • ⚡️ Smart: Async requests will be cached.
  • 🚀 SSR: Render a loader until the DOM is available
  • 🟦 Typescript: Nicely typed


npm i react-inlinesvg

And import it into your code:

import React from 'react';
import SVG from 'react-inlinesvg';

export default function App() {
  return (


src {string} - required.
The SVG file you want to load. It can be a require, URL or a string (base64 or url encoded). If you are using create-react-app and your file resides in the public directory you can use the path directly without require.

baseURL {string}
An URL to prefix each ID in case you are using the <base> tag and uniquifyIDs.

children {ReactNode}
The fallback content in case of a fetch error or unsupported browser.

<SVG src="...">
    <img src="..." alt="fallback" />

cacheRequests {boolean} ▶︎ true
Cache remote SVGs.

description {string}
A description for your SVG. It will override an existing <desc> tag.

fetchOptions {RequestInit}
Custom options for the request.

innerRef {React.Ref}
Set a ref in SVGElement.

loader {node}
A component to be shown while the SVG is loading.

onError {function}
A callback to be invoked if loading the SVG fails.
This will receive a single argument with:

  • a FetchError with:
  message: string;
  type: string;
  errno: string;
  code: string;
  • or an InlineSVGError, which has the following properties:
  name: 'InlineSVGError';
  data: object; // optional
  message: string;

onLoad {function}.
A callback to be invoked upon successful load.
This will receive 2 arguments: the src prop and a hasCache boolean

preProcessor {function} ▶︎ string
A function to process the contents of the SVG text before parsing.

title {string}
A title for your SVG. It will override an existing <title> tag.

uniqueHash {string} ▶︎ a random 8 characters string [A-Za-z0-9]
A string to use with uniquifyIDs.

uniquifyIDs {boolean} ▶︎ false
Create unique IDs for each icon.

Any additional props will be passed down to the SVG element.


  description="The React logo"
  onError={(error) => console.log(error.message)}
  onLoad={(src, hasCache) => console.log(src, hasCache)}
  preProcessor={(code) => code.replace(/fill=".*?"/g, 'fill="currentColor"')}


The internal cache is exported as cacheStore if you need to debug or pre-cache some files.
⚠️ Use it at your own risk.

Browser Support

Any browsers that support inlining SVGs and fetch will work.

If you need to support legacy browsers you'll need to include a polyfiil for fetch and Number.isNaN in your app. Take a look at react-app-polyfill or polyfill.io.


If you are loading remote SVGs, you'll need to make sure it has CORS support.

Why you need this package?

One of the reasons SVGs are awesome is because you can style them with CSS. Unfortunately, this winds up not being too useful in practice because the style element has to be in the same document. This leaves you with three bad options:

  1. Embed the CSS in the SVG document
    • Can't use your CSS preprocessors (LESS, SASS)
    • Can't target parent elements (button hover, etc.)
    • Makes maintenance difficult
  2. Link to a CSS file in your SVG document
    • Sharing styles with your HTML means duplicating paths across your project, making maintenance a pain
    • Not sharing styles with your HTML means extra HTTP requests (and likely duplicating paths between different SVGs)
    • Still can't target parent elements
    • Your SVG becomes coupled to your external stylesheet, complicating reuse.
  3. Embed the SVG in your HTML
    • Bloats your HTML
    • SVGs can't be cached by browsers between pages.
    • A maintenance nightmare

But there's an alternative that sidesteps these issues: load the SVG with a GET request and then embed it in the document. This is what this component does.


The SVG <use> element can be used to achieve something similar to this component. See this article for more information and this table for browser support and caveats.


Thanks to @matthewwithanm for creating this component and so kindly transfer it to me. I'll definitely keep the good work! ❤️