react-content-loader, react-loading-skeleton, and react-placeholder are all React libraries designed to create placeholder loading states, often called skeleton screens. These components improve perceived performance by showing a structured layout while data fetches, reducing layout shift and user anxiety. react-content-loader uses SVG to draw custom shapes, offering pixel-perfect control. react-loading-skeleton relies on CSS animations for a simple, box-based approach that is easy to drop in. react-placeholder acts as a wrapper component that swaps between a template and actual content, focusing on structural replacement rather than visual animation details.
When building modern React applications, showing a loading spinner is no longer enough. Users expect to see the structure of the page immediately, even before data arrives. This technique, known as skeleton screens, reduces perceived wait time and prevents layout shifts. react-content-loader, react-loading-skeleton, and react-placeholder solve this problem in different ways. Let's compare how they handle rendering, customization, and implementation.
The core difference lies in how these libraries draw the loading state on the screen.
react-content-loader uses SVG elements to draw shapes.
// react-content-loader: SVG based
import ContentLoader from "react-content-loader"
const CardLoader = () => (
<ContentLoader width={300} height={100}>
<rect x="10" y="10" rx="5" ry="5" width="200" height="20" />
<rect x="10" y="40" rx="5" ry="5" width="150" height="10" />
</ContentLoader>
)
react-loading-skeleton uses CSS animations on div elements.
// react-loading-skeleton: CSS based
import Skeleton from "react-loading-skeleton"
const CardLoader = () => (
<div>
<Skeleton width={200} height={20} />
<Skeleton width={150} height={10} />
</div>
)
react-placeholder uses a wrapper component to swap content.
// react-placeholder: Wrapper based
import Placeholder from "react-placeholder"
const CardLoader = ({ loading }) => (
<Placeholder loading={loading} template={<div className="skeleton-box" />}>
<ActualCardContent />
</Placeholder>
)
How much effort do you need to make the loader look like your actual content?
react-content-loader requires you to draw the layout.
// react-content-loader: Precise coordinates
<ContentLoader width={400} height={200}>
<circle cx="30" cy="30" r="30" />
<rect x="80" y="20" width="200" height="20" />
<rect x="80" y="60" width="150" height="10" />
</ContentLoader>
react-loading-skeleton relies on box dimensions.
// react-loading-skeleton: Dimension based
<Skeleton circle={true} height={60} width={60} />
<Skeleton count={3} height={20} />
react-placeholder depends on your template definition.
// react-placeholder: Template component
const Template = () => <div className="my-custom-loader">Loading...</div>
<Placeholder loading={true} template={<Template />}>
<Content />
</Placeholder>
Where does the loader sit in your component tree?
react-content-loader is typically a standalone component.
// react-content-loader: Conditional render
{isLoading ? <CardLoader /> : <CardData />}
react-loading-skeleton can be inline or standalone.
// react-loading-skeleton: Inline usage
<div>
{isLoading ? <Skeleton /> : <h1>{title}</h1>}
</div>
react-placeholder is strictly a wrapper.
// react-placeholder: Wrapper pattern
<Placeholder loading={isLoading} template={<Loader />}>
<CardData />
</Placeholder>
Long-term support matters when choosing a dependency.
react-content-loader is highly active and widely adopted.
react-loading-skeleton is also actively maintained.
react-placeholder has lower recent activity.
| Feature | react-content-loader | react-loading-skeleton | react-placeholder |
|---|---|---|---|
| Rendering | 🎨 SVG Shapes | 🟦 CSS Boxes | 🔄 Component Wrapper |
| Customization | 🔧 High (Coordinates) | ⚙️ Medium (Dimensions) | 🧩 High (Templates) |
| Setup Effort | 🕒 Higher | ⚡ Low | ⚙️ Medium |
| Visual Fidelity | ✅ Exact Match | ⚠️ Approximate | ✅ Depends on Template |
| Maintenance | 🟢 Active | 🟢 Active | 🟡 Less Active |
For most modern React applications, react-loading-skeleton is the best starting point. It offers the best balance between effort and result — you get a polished loading state with minimal code. Use it for dashboards, admin panels, and standard content feeds.
Choose react-content-loader when design precision is a requirement. If your marketing site or public-facing app needs the loading state to match the final UI exactly, the SVG approach is worth the extra setup time.
Use react-placeholder primarily if you are maintaining an existing codebase that already relies on it. For new projects, the other two options offer better long-term support and more flexible integration patterns.
Final Thought: All three libraries solve the same user experience problem — preventing blank screens during data fetches. The right choice depends on how much control you need over the visual details versus how quickly you need to ship.
Choose react-content-loader if you need precise visual control over the loading state. It is ideal for matching complex UI layouts where standard boxes look out of place. Use this when design fidelity is critical and you have the time to draw custom SVG shapes.
Choose react-loading-skeleton for most standard applications where speed and simplicity matter. It works well for lists, cards, and text blocks where a generic rectangular pulse is acceptable. This is the best choice for teams that want a dependency with minimal configuration.
Choose react-placeholder if you prefer a wrapper pattern that toggles between a template and children. It suits legacy projects or specific architectures where you define a full component template for the loading state. However, evaluate newer alternatives for modern projects due to lower maintenance activity.
SVG-Powered component to easily create placeholder loadings (like Facebook's cards loading).
npm i react-content-loader --save
yarn add react-content-loader
npm i react-content-loader react-native-svg --save
yarn add react-content-loader react-native-svg
CDN from JSDELIVR
There are two ways to use it:
1. Presets, see the examples:
import ContentLoader, { Facebook } from 'react-content-loader'
const MyLoader = () => <ContentLoader />
const MyFacebookLoader = () => <Facebook />
2. Custom mode, see the online tool
const MyLoader = () => (
<ContentLoader viewBox="0 0 380 70">
{/* Only SVG shapes */}
<rect x="0" y="0" rx="5" ry="5" width="70" height="70" />
<rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
<rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
</ContentLoader>
)
Still not clear? Take a look at this working example at codesandbox.io Or try the components editable demo hands-on and install it from bit.dev
react-content-loader can be used with React Native in the same way as web version with the same import:
1. Presets, see the examples:
import ContentLoader, { Facebook } from 'react-content-loader/native'
const MyLoader = () => <ContentLoader />
const MyFacebookLoader = () => <Facebook />
2. Custom mode
To create custom loaders there is an important difference: as React Native doesn't have any native module for SVG components, it's necessary to import the shapes from react-native-svg or use the named export Rect and Circle from react-content-loader import:
import ContentLoader, { Rect, Circle } from 'react-content-loader/native'
const MyLoader = () => (
<ContentLoader viewBox="0 0 380 70">
<Circle cx="30" cy="30" r="30" />
<Rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
<Rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
</ContentLoader>
)
Prop name and type | Environment | Description |
|---|---|---|
animate?: boolean Defaults to true | React DOM React Native | Opt-out of animations with false |
title?: string Defaults to Loading... | React DOM only | It's used to describe what element it is. Use '' (empty string) to remove. |
baseUrl?: stringDefaults to an empty string | React DOM only | Required if you're using <base url="/" /> document <head/>. This prop is common used as: <ContentLoader baseUrl={window.location.pathname} /> which will fill the SVG attribute with the relative path. Related #93. |
speed?: number Defaults to 1.2 | React DOM React Native | Animation speed in seconds. |
viewBox?: string Defaults to undefined | React DOM React Native | Use viewBox props to set a custom viewBox value, for more information about how to use it, read the article How to Scale SVG. |
gradientRatio?: number Defaults to 1.2 | React DOM only | Width of the animated gradient as a fraction of the view box width. |
rtl?: boolean Defaults to false | React DOM React Native | Content right-to-left. |
backgroundColor?: string Defaults to #f5f6f7 | React DOM React Native | Used as background of animation. |
foregroundColor?: string Defaults to #eee | React DOM React Native | Used as the foreground of animation. |
backgroundOpacity?: number Defaults to 1 | React DOM React Native | Background opacity (0 = transparent, 1 = opaque) used to solve an issue in Safari |
foregroundOpacity?: number Defaults to 1 | React DOM React Native | Animation opacity (0 = transparent, 1 = opaque) used to solve an issue in Safari |
style?: React.CSSProperties Defaults to {} | React DOM only | |
uniqueKey?: string Defaults to random unique id | React DOM only | Use the same value of prop key, that will solve inconsistency on the SSR, see more here. |
beforeMask?: JSX.Element Defaults to null | React DOM React Native | Define custom shapes before content, see more here. |
See all options live
import { Facebook } from 'react-content-loader'
const MyFacebookLoader = () => <Facebook />
import { Instagram } from 'react-content-loader'
const MyInstagramLoader = () => <Instagram />
import { Code } from 'react-content-loader'
const MyCodeLoader = () => <Code />
import { List } from 'react-content-loader'
const MyListLoader = () => <List />
import { BulletList } from 'react-content-loader'
const MyBulletListLoader = () => <BulletList />
For the custom mode, use the online tool.
const MyLoader = () => (
<ContentLoader
height={140}
speed={1}
backgroundColor={'#333'}
foregroundColor={'#999'}
viewBox="0 0 380 70"
>
{/* Only SVG shapes */}
<rect x="0" y="0" rx="5" ry="5" width="70" height="70" />
<rect x="80" y="17" rx="4" ry="4" width="300" height="13" />
<rect x="80" y="40" rx="3" ry="3" width="250" height="10" />
</ContentLoader>
)

In order to avoid unexpected behavior, the package doesn't have opinioned settings. So if it needs to be responsive, have in mind that the output of the package is a regular SVG, so it just needs the same attributes to become a regular SVG responsive, which means:
import { Code } from 'react-content-loader'
const MyCodeLoader = () => (
<Code
width={100}
height={100}
viewBox="0 0 100 100"
style={{ width: '100%' }}
/>
)
As the main component generates random values to match the id of the SVG element with background style, it can encounter unexpected errors and unmatching warning on render, once the random value of id will be generated twice, in case of SSR: server and client; or in case of snapshot test: on the first match and re-running the test.
To fix it, set the prop uniqueKey, then the id will not be random anymore:
import { Facebook } from 'react-content-loader'
const MyFacebookLoader = () => <Facebook uniqueKey="my-random-value" />
When using rgba as a backgroundColor or foregroundColor value, Safari does not respect the alpha channel, meaning that the color will be opaque. To prevent this, instead of using a rgba value for backgroundColor/foregroundColor, use the rgb equivalent and move the alpha channel value to the backgroundOpacity/foregroundOpacity props.
{/* Opaque color in Safari and iOS */}
<ContentLoader
backgroundColor="rgba(0,0,0,0.06)"
foregroundColor="rgba(0,0,0,0.12)">
{/_ Semi-transparent color in Safari and iOS _/}
<ContentLoader
backgroundColor="rgb(0,0,0)"
foregroundColor="rgb(0,0,0)"
backgroundOpacity={0.06}
foregroundOpacity={0.12}>
Using the base tag on a page that contains SVG elements fails to render and it looks like a black box. Just remove the base-href tag from the <head /> and the issue has been solved.
Old browsers don't support animation in SVG (compatibility list), and if your project must support IE, for examples, here's a couple of ways to make sure that browser supports SVG Animate:
window.SVGAnimateElementdocument.implementation.hasFeature("http://www.w3.org/TR/SVG11/feature#SVG-Animation", "1.1")Fork the repo and then clone it
$ git clone git@github.com:YourUsername/react-content-loader.git && cd react-content-loader
$ npm i: Install the dependencies;
$ npm run build: Build to production;
$ npm run dev: Run the Storybook to see your changes;
$ npm run test: Run all tests: type checking, unit tests on web and native;
$ npm run test:watch: Watch unit tests;
As React Native doesn't support symbolic links (to link the dependency to another folder) and as there is no playground to check your contributions (like storybook), this is recommended strategy to run the project locally:
yarn add react-content-loader react-native-svgreact-content-loader to the project just cloned, like:
import ContentLoader, { Rect, Circle } from './react-content-loader/native'Commit messages should follow the commit message convention so, changelogs could be generated automatically by that. Commit messages are validated automatically upon commit. If you aren't familiar with the commit message convention, you can use yarn commit (or npm run commit) instead of git commit, which provides an interactive CLI for generating proper commit messages.