file-loader, image-webpack-loader, raw-loader, and url-loader are Webpack loaders designed to handle non-JavaScript assets during the build process. file-loader emits files to the output directory and returns their public paths, url-loader conditionally inlines small files as Data URLs, raw-loader imports file contents as strings, and image-webpack-loader compresses and optimizes image assets. However, as of Webpack 5, file-loader, raw-loader, and url-loader are officially deprecated in favor of Webpack's built-in Asset Modules, while image-webpack-loader remains actively maintained for image optimization tasks.
These four loaders — file-loader, image-webpack-loader, raw-loader, and url-loader — are all designed to help Webpack handle non-JavaScript assets during the build process. However, they serve very different purposes, and some have been deprecated in favor of newer Webpack features. Understanding when and how to use each is critical for optimizing asset handling, bundle size, and developer experience.
Before diving into functionality, it’s essential to note that three of these four packages are officially deprecated:
file-loader: Deprecated as of Webpack 5. Use built-in asset modules instead.raw-loader: Deprecated as of Webpack 5. Use type: 'asset/source'.url-loader: Deprecated as of Webpack 5. Replaced by type: 'asset/inline' or type: 'asset' with dataUrlCondition.Only image-webpack-loader remains actively maintained — but it serves a completely different role: image optimization, not asset resolution.
🛑 Do not use
file-loader,raw-loader, orurl-loaderin new Webpack 5+ projects. They exist only for legacy compatibility.
file-loader: Emit files to output directoryfile-loader copies a file to your output directory and returns its public path as a string. It was commonly used for images, fonts, or other static assets that should live as separate files.
// webpack.config.js (legacy)
module.exports = {
module: {
rules: [
{
test: /\.(png|jpe?g|gif)$/i,
use: ['file-loader']
}
]
}
};
// In code
import img from './image.png';
console.log(img); // e.g., '/static/media/image.abc123.png'
url-loader: Inline small files as Data URLsurl-loader works like file-loader, but with a twist: if a file is smaller than a configured limit, it returns a base64-encoded Data URL instead of emitting a file. This avoids extra HTTP requests for tiny assets.
// webpack.config.js (legacy)
{
test: /\.(png|jpe?g|gif)$/i,
use: [
{
loader: 'url-loader',
options: { limit: 8192 } // 8 KB
}
]
}
// For small image → returns 'data:image/png;base64,...'
// For large image → falls back to file-loader behavior
raw-loader: Import file contents as a stringraw-loader reads a file and exports its raw content as a JavaScript string. Useful for importing text files, SVGs, or shader code without parsing.
// webpack.config.js (legacy)
{
test: /\.txt$/,
use: 'raw-loader'
}
// In code
import license from './LICENSE.txt';
console.log(typeof license); // 'string'
image-webpack-loader: Optimize image assetsUnlike the others, image-webpack-loader doesn’t change how assets are resolved — it compresses and optimizes images using tools like mozjpeg, pngquant, and svgo. It’s typically chained after another loader.
// webpack.config.js (still valid)
{
test: /\.(png|jpe?g|gif|svg)$/i,
use: [
'file-loader', // or Webpack 5 asset module
{
loader: 'image-webpack-loader',
options: {
mozjpeg: { quality: 80 },
pngquant: { quality: [0.6, 0.8] }
}
}
]
}
Webpack 5 introduced Asset Modules, which eliminate the need for file-loader, url-loader, and raw-loader. Here’s how to migrate:
file-loader → type: 'asset/resource'// Modern equivalent
{
test: /\.(png|jpg|gif)$/i,
type: 'asset/resource'
}
url-loader → type: 'asset' with parser.dataUrlCondition// Modern equivalent
{
test: /\.(png|jpg|gif)$/i,
type: 'asset',
parser: {
dataUrlCondition: { maxSize: 8 * 1024 } // 8 KB
}
}
raw-loader → type: 'asset/source'// Modern equivalent
{
test: /\.txt$/,
type: 'asset/source'
}
💡 You can still use
image-webpack-loaderwith these modern asset types — just place it in theusearray alongside them.
Here’s how you’d configure image loading and optimization in a modern Webpack 5 project:
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpe?g|gif|svg)$/i,
type: 'asset',
parser: {
dataUrlCondition: { maxSize: 4 * 1024 } // Inline <4KB
},
generator: {
filename: 'images/[name].[hash][ext]'
},
use: [
{
loader: 'image-webpack-loader',
options: {
disable: process.env.NODE_ENV === 'development',
mozjpeg: { progressive: true, quality: 75 },
optipng: { enabled: false },
pngquant: { quality: [0.65, 0.8], speed: 4 },
svgo: { plugins: [{ removeViewBox: false }] }
}
}
]
}
]
}
};
This setup:
/images/image-webpack-loader TodaySince the other three loaders are deprecated, the only relevant decision is whether to include image-webpack-loader:
✅ Use it if:
❌ Skip it if:
If you’re maintaining a Webpack 4 project:
file-loader, url-loader, or raw-loader.image-webpack-loader if you rely on its optimization — it works fine with Webpack 5 asset modules.| Package | Status | Purpose | Webpack 5 Replacement |
|---|---|---|---|
file-loader | ❌ Deprecated | Emit file, return public path | type: 'asset/resource' |
url-loader | ❌ Deprecated | Inline small files as Data URLs | type: 'asset' + dataUrlCondition |
raw-loader | ❌ Deprecated | Import file contents as string | type: 'asset/source' |
image-webpack-loader | ✅ Active | Compress/optimize image assets | No replacement needed |
For new projects, skip the deprecated loaders entirely and use Webpack 5’s built-in asset modules. Add image-webpack-loader only if you need on-the-fly image optimization and don’t have a better solution (like a smart CDN).
For existing projects, plan a migration away from the deprecated loaders when moving to Webpack 5. The configuration changes are straightforward, and you’ll benefit from reduced dependencies and better integration with Webpack’s core.
Do not use url-loader in modern Webpack projects — it’s deprecated. Replace it with type: 'asset' combined with parser.dataUrlCondition.maxSize to inline small assets as Data URLs. Its functionality is now natively supported without extra dependencies.
Avoid raw-loader in new projects — it’s deprecated as of Webpack 5. Use type: 'asset/source' instead to import file contents as strings. This package should only be used in legacy Webpack 4 codebases where migration isn’t feasible yet.
Choose image-webpack-loader when you need automated, build-time image optimization (compression, resizing, format conversion) and don’t have a CDN or external service handling it. It works well alongside Webpack 5’s asset modules and is the only actively maintained package among the four. Avoid it if your images are already optimized or if build performance is more critical than output size.
Do not use file-loader in new Webpack 5+ projects — it is officially deprecated. Instead, use Webpack’s built-in type: 'asset/resource' to emit files to the output directory. Only consider this package if you’re maintaining a legacy Webpack 4 project and cannot upgrade immediately.
A loader for webpack which transforms files into base64 URIs.
To begin, you'll need to install url-loader:
$ npm install url-loader --save-dev
url-loader works like
file-loader, but can return
a DataURL if the file is smaller than a byte limit.
index.js
import img from './image.png';
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
limit: 8192,
},
},
],
},
],
},
};
And run webpack via your preferred method.
| Name | Type | Default | Description |
|---|---|---|---|
limit | {Boolean|Number|String} | true | Specifying the maximum size of a file in bytes. |
mimetype | {Boolean|String} | based from mime-types | Sets the MIME type for the file to be transformed. |
encoding | {Boolean|String} | base64 | Specify the encoding which the file will be inlined with. |
generator | {Function} | () => type/subtype;encoding,base64_data | You can create you own custom implementation for encoding data. |
fallback | {String} | file-loader | Specifies an alternative loader to use when a target file's size exceeds the limit. |
esModule | {Boolean} | true | Use ES modules syntax. |
limitType: Boolean|Number|String
Default: undefined
The limit can be specified via loader options and defaults to no limit.
BooleanEnable or disable transform files into base64.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
limit: false,
},
},
],
},
],
},
};
Number|StringA Number or String specifying the maximum size of a file in bytes.
If the file size is equal or greater than the limit file-loader will be used (by default) and all query parameters are passed to it.
Using an alternative to file-loader is enabled via the fallback option.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
limit: 8192,
},
},
],
},
],
},
};
mimetypeType: Boolean|String
Default: based from mime-types
Specify the mimetype which the file will be inlined with.
If unspecified the mimetype value will be used from mime-types.
BooleanThe true value allows to generation the mimetype part from mime-types.
The false value removes the mediatype part from a Data URL (if omitted, defaults to text/plain;charset=US-ASCII).
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
mimetype: false,
},
},
],
},
],
},
};
StringSets the MIME type for the file to be transformed.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
mimetype: 'image/png',
},
},
],
},
],
},
};
encodingType: Boolean|String
Default: base64
Specify the encoding which the file will be inlined with.
If unspecified the encoding will be base64.
BooleanIf you don't want to use any encoding you can set encoding to false however if you set it to true it will use the default encoding base64.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.svg$/i,
use: [
{
loader: 'url-loader',
options: {
encoding: false,
},
},
],
},
],
},
};
StringIt supports Node.js Buffers and Character Encodings which are ["utf8","utf16le","latin1","base64","hex","ascii","binary","ucs2"].
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.svg$/i,
use: [
{
loader: 'url-loader',
options: {
encoding: 'utf8',
},
},
],
},
],
},
};
generatorType: Function
Default: (mimetype, encoding, content, resourcePath) => mimetype;encoding,base64_content
You can create you own custom implementation for encoding data.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|html)$/i,
use: [
{
loader: 'url-loader',
options: {
// The `mimetype` and `encoding` arguments will be obtained from your options
// The `resourcePath` argument is path to file.
generator: (content, mimetype, encoding, resourcePath) => {
if (/\.html$/i.test(resourcePath)) {
return `data:${mimetype},${content.toString()}`;
}
return `data:${mimetype}${
encoding ? `;${encoding}` : ''
},${content.toString(encoding)}`;
},
},
},
],
},
],
},
};
fallbackType: String
Default: 'file-loader'
Specifies an alternative loader to use when a target file's size exceeds the limit set in the limit option.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
fallback: require.resolve('responsive-loader'),
},
},
],
},
],
},
};
The fallback loader will receive the same configuration options as url-loader.
For example, to set the quality option of a responsive-loader above use:
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.(png|jpg|gif)$/i,
use: [
{
loader: 'url-loader',
options: {
fallback: require.resolve('responsive-loader'),
quality: 85,
},
},
],
},
],
},
};
esModuleType: Boolean
Default: true
By default, file-loader generates JS modules that use the ES modules syntax.
There are some cases in which using ES modules is beneficial, like in the case of module concatenation and tree shaking.
You can enable a CommonJS module syntax using:
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [
{
loader: 'url-loader',
options: {
esModule: false,
},
},
],
},
],
},
};
SVG can be compressed into a more compact output, avoiding base64.
You can read about it more here.
You can do it using mini-svg-data-uri package.
webpack.config.js
const svgToMiniDataURI = require('mini-svg-data-uri');
module.exports = {
module: {
rules: [
{
test: /\.svg$/i,
use: [
{
loader: 'url-loader',
options: {
generator: (content) => svgToMiniDataURI(content.toString()),
},
},
],
},
],
},
};
Please take a moment to read our contributing guidelines if you haven't yet done so.