file-loader vs url-loader vs raw-loader vs image-webpack-loader
Webpack Loaders for Asset Management Comparison
1 Year
file-loaderurl-loaderraw-loaderimage-webpack-loaderSimilar Packages:
What's Webpack Loaders for Asset Management?

Webpack loaders are essential tools that allow developers to preprocess files as they are added to a bundle. They enable the handling of various asset types, such as images, fonts, and raw files, making it easier to manage and optimize these resources in web applications. Each loader serves a specific purpose, allowing for tailored processing based on the asset type, which ultimately enhances the performance and organization of the application.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
file-loader10,134,2111,864-14 years agoMIT
url-loader5,027,9011,403-44 years agoMIT
raw-loader3,290,093844-54 years agoMIT
image-webpack-loader109,6342,0263.56 MB81-MIT
Feature Comparison: file-loader vs url-loader vs raw-loader vs image-webpack-loader

File Handling

  • file-loader:

    file-loader copies files to the output directory and returns the public URL of the file. It is straightforward and works well for static assets that do not require any transformation before being included in the build.

  • url-loader:

    url-loader can inline files as base64 URIs if they are below a specified size limit, reducing the number of requests made to the server. For larger files, it falls back to file-loader, making it a versatile choice for handling both small and large assets.

  • raw-loader:

    raw-loader imports files as strings, allowing developers to access the raw content of files directly in their JavaScript code. This is particularly useful for embedding text or markup files directly into components without any parsing or transformation.

  • image-webpack-loader:

    image-webpack-loader optimizes images by applying various compression techniques, such as lossless and lossy compression, ensuring that images are as small as possible without sacrificing quality. It can be configured to work with multiple image formats and can be chained with other loaders for further processing.

Optimization Capabilities

  • file-loader:

    file-loader does not provide any optimization capabilities; it simply copies the files as they are. This makes it suitable for scenarios where files do not require processing, but it lacks the ability to reduce file sizes or improve performance.

  • url-loader:

    url-loader provides optimization by inlining small files, which can reduce the number of HTTP requests. However, it does not optimize the files themselves; for that, it relies on other loaders like image-webpack-loader.

  • raw-loader:

    raw-loader does not perform any optimization; it simply reads the content of files as strings. This is useful for scenarios where the content needs to be displayed as-is, but it does not contribute to performance enhancements.

  • image-webpack-loader:

    image-webpack-loader excels in optimizing images by applying various techniques like resizing, compressing, and converting formats. It significantly reduces the size of image files, which can lead to faster load times and improved performance on web pages.

Use Cases

  • file-loader:

    file-loader is best used for static assets like images, fonts, and other files that need to be included in the final build without any transformation. It is straightforward and effective for cases where file processing is not necessary.

  • url-loader:

    url-loader is versatile and can be used for both small and large assets. It is particularly useful in projects where reducing the number of HTTP requests is important, such as single-page applications or those with many small images.

  • raw-loader:

    raw-loader is suited for scenarios where you need to import text files, templates, or markdown directly into your JavaScript code. It is often used in applications that require dynamic content rendering from external files.

  • image-webpack-loader:

    image-webpack-loader is ideal for projects that require image optimization, such as websites with many images where performance is critical. It is particularly useful for e-commerce sites or portfolios where image quality and load times are essential.

Configuration Complexity

  • file-loader:

    file-loader is simple to configure, requiring minimal setup to get started. It is straightforward and does not involve complex options, making it accessible for beginners.

  • url-loader:

    url-loader has a moderate configuration complexity, as it requires specifying a limit for inlining files. While it is not overly complicated, it does require some understanding of how to balance inlining small files versus using file-loader for larger ones.

  • raw-loader:

    raw-loader is easy to configure, with a simple setup that allows for quick integration into projects. It is straightforward and requires little additional configuration, making it beginner-friendly.

  • image-webpack-loader:

    image-webpack-loader can be more complex to configure due to its various optimization options and the need to chain it with other loaders. However, this complexity allows for fine-tuned control over image processing, making it powerful for advanced users.

Performance Impact

  • file-loader:

    file-loader has a minimal performance impact since it simply copies files without any processing. However, it does not contribute to performance optimization, which may be a drawback for performance-sensitive applications.

  • url-loader:

    url-loader can improve performance by reducing the number of HTTP requests for small files, which can lead to faster load times. However, for larger files, it falls back to file-loader, which does not optimize performance.

  • raw-loader:

    raw-loader has a negligible performance impact, as it merely reads file content without any processing. However, it does not enhance performance, so it should be used in contexts where file content needs to be directly accessed.

  • image-webpack-loader:

    image-webpack-loader significantly improves performance by reducing image sizes through optimization techniques. Smaller images lead to faster load times and better overall performance, making it a valuable addition to any project that uses images extensively.

How to Choose: file-loader vs url-loader vs raw-loader vs image-webpack-loader
  • file-loader:

    Choose file-loader when you want to copy files to the output directory and return their URLs. It is ideal for handling static assets like images and fonts that need to be included in the final build without any transformation.

  • url-loader:

    Opt for url-loader when you want the flexibility of inline assets as base64 URIs for small files, while falling back to file-loader for larger files. This loader is beneficial for optimizing the number of HTTP requests by inlining small files directly into the JavaScript bundle.

  • raw-loader:

    Use raw-loader when you need to import files as strings, such as text files or markdown. This loader is useful for scenarios where the content of the file needs to be processed or displayed directly in the application without any transformation.

  • image-webpack-loader:

    Select image-webpack-loader for optimizing images during the build process. It provides a range of image compression techniques and can be used in conjunction with other loaders to ensure images are not only included but also optimized for performance.

README for file-loader

npm node deps tests coverage chat size

file-loader

The file-loader resolves import/require() on a file into a url and emits the file into the output directory.

Getting Started

To begin, you'll need to install file-loader:

$ npm install file-loader --save-dev

Import (or require) the target file(s) in one of the bundle's files:

file.js

import img from './file.png';

Then add the loader to your webpack config. For example:

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
          },
        ],
      },
    ],
  },
};

And run webpack via your preferred method. This will emit file.png as a file in the output directory (with the specified naming convention, if options are specified to do so) and returns the public URI of the file.

ℹ️ By default the filename of the resulting file is the hash of the file's contents with the original extension of the required resource.

Options

name

Type: String|Function Default: '[contenthash].[ext]'

Specifies a custom filename template for the target file(s) using the query parameter name. For example, to emit a file from your context directory into the output directory retaining the full directory structure, you might use:

String

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          name: '[path][name].[ext]',
        },
      },
    ],
  },
};

Function

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          name(resourcePath, resourceQuery) {
            // `resourcePath` - `/absolute/path/to/file.js`
            // `resourceQuery` - `?foo=bar`

            if (process.env.NODE_ENV === 'development') {
              return '[path][name].[ext]';
            }

            return '[contenthash].[ext]';
          },
        },
      },
    ],
  },
};

ℹ️ By default the path and name you specify will output the file in that same directory, and will also use the same URI path to access the file.

outputPath

Type: String|Function Default: undefined

Specify a filesystem path where the target file(s) will be placed.

String

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          outputPath: 'images',
        },
      },
    ],
  },
};

Function

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          outputPath: (url, resourcePath, context) => {
            // `resourcePath` is original absolute path to asset
            // `context` is directory where stored asset (`rootContext`) or `context` option

            // To get relative path you can use
            // const relativePath = path.relative(context, resourcePath);

            if (/my-custom-image\.png/.test(resourcePath)) {
              return `other_output_path/${url}`;
            }

            if (/images/.test(context)) {
              return `image_output_path/${url}`;
            }

            return `output_path/${url}`;
          },
        },
      },
    ],
  },
};

publicPath

Type: String|Function Default: __webpack_public_path__+outputPath

Specifies a custom public path for the target file(s).

String

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          publicPath: 'assets',
        },
      },
    ],
  },
};

Function

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        loader: 'file-loader',
        options: {
          publicPath: (url, resourcePath, context) => {
            // `resourcePath` is original absolute path to asset
            // `context` is directory where stored asset (`rootContext`) or `context` option

            // To get relative path you can use
            // const relativePath = path.relative(context, resourcePath);

            if (/my-custom-image\.png/.test(resourcePath)) {
              return `other_public_path/${url}`;
            }

            if (/images/.test(context)) {
              return `image_output_path/${url}`;
            }

            return `public_path/${url}`;
          },
        },
      },
    ],
  },
};

postTransformPublicPath

Type: Function Default: undefined

Specifies a custom function to post-process the generated public path. This can be used to prepend or append dynamic global variables that are only available at runtime, like __webpack_public_path__. This would not be possible with just publicPath, since it stringifies the values.

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpg|gif)$/i,
        loader: 'file-loader',
        options: {
          publicPath: '/some/path/',
          postTransformPublicPath: (p) => `__webpack_public_path__ + ${p}`,
        },
      },
    ],
  },
};

context

Type: String Default: context

Specifies a custom file context.

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              context: 'project',
            },
          },
        ],
      },
    ],
  },
};

emitFile

Type: Boolean Default: true

If true, emits a file (writes a file to the filesystem). If false, the loader will return a public URI but will not emit the file. It is often useful to disable this option for server-side packages.

file.js

// bundle file
import img from './file.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              emitFile: false,
            },
          },
        ],
      },
    ],
  },
};

regExp

Type: RegExp Default: undefined

Specifies a Regular Expression to one or many parts of the target file path. The capture groups can be reused in the name property using [N] placeholder.

file.js

import img from './customer01/file.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              regExp: /\/([a-z0-9]+)\/[a-z0-9]+\.png$/i,
              name: '[1]-[name].[ext]',
            },
          },
        ],
      },
    ],
  },
};

ℹ️ If [0] is used, it will be replaced by the entire tested string, whereas [1] will contain the first capturing parenthesis of your regex and so on...

esModule

Type: 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: 'file-loader',
            options: {
              esModule: false,
            },
          },
        ],
      },
    ],
  },
};

Placeholders

Full information about placeholders you can find here.

[ext]

Type: String Default: file.extname

The file extension of the target file/resource.

[name]

Type: String Default: file.basename

The basename of the file/resource.

[path]

Type: String Default: file.directory

The path of the resource relative to the webpack/config context.

[folder]

Type: String Default: file.folder

The folder of the resource is in.

[query]

Type: String Default: file.query

The query of the resource, i.e. ?foo=bar.

[emoji]

Type: String Default: undefined

A random emoji representation of content.

[emoji:<length>]

Type: String Default: undefined

Same as above, but with a customizable number of emojis

[hash]

Type: String Default: md4

Specifies the hash method to use for hashing the file content.

[contenthash]

Type: String Default: md4

Specifies the hash method to use for hashing the file content.

[<hashType>:hash:<digestType>:<length>]

Type: String

The hash of options.content (Buffer) (by default it's the hex digest of the hash).

digestType

Type: String Default: 'hex'

The digest that the hash function should use. Valid values include: base26, base32, base36, base49, base52, base58, base62, base64, and hex.

hashType

Type: String Default: 'md4'

The type of hash that the has function should use. Valid values include: md4, md5, sha1, sha256, and sha512.

length

Type: Number Default: undefined

Users may also specify a length for the computed hash.

[N]

Type: String Default: undefined

The n-th match obtained from matching the current file name against the regExp.

Examples

Names

The following examples show how one might use file-loader and what the result would be.

file.js

import png from './image.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              name: 'dirname/[contenthash].[ext]',
            },
          },
        ],
      },
    ],
  },
};

Result:

# result
dirname/0dcbbaa701328ae351f.png

file.js

import png from './image.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              name: '[sha512:hash:base64:7].[ext]',
            },
          },
        ],
      },
    ],
  },
};

Result:

# result
gdyb21L.png

file.js

import png from './path/to/file.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              name: '[path][name].[ext]?[contenthash]',
            },
          },
        ],
      },
    ],
  },
};

Result:

# result
path/to/file.png?e43b20c069c4a01867c31e98cbce33c9

CDN

The following examples show how to use file-loader for CDN uses query params.

file.js

import png from './directory/image.png?width=300&height=300';

webpack.config.js

module.exports = {
  output: {
    publicPath: 'https://cdn.example.com/',
  },
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif)$/i,
        use: [
          {
            loader: 'file-loader',
            options: {
              name: '[path][name].[ext][query]',
            },
          },
        ],
      },
    ],
  },
};

Result:

# result
https://cdn.example.com/directory/image.png?width=300&height=300

Dynamic public path depending on environment variable at run time

An application might want to configure different CDN hosts depending on an environment variable that is only available when running the application. This can be an advantage, as only one build of the application is necessary, which behaves differently depending on environment variables of the deployment environment. Since file-loader is applied when compiling the application, and not when running it, the environment variable cannot be used in the file-loader configuration. A way around this is setting the __webpack_public_path__ to the desired CDN host depending on the environment variable at the entrypoint of the application. The option postTransformPublicPath can be used to configure a custom path depending on a variable like __webpack_public_path__.

main.js

const assetPrefixForNamespace = (namespace) => {
  switch (namespace) {
    case 'prod':
      return 'https://cache.myserver.net/web';
    case 'uat':
      return 'https://cache-uat.myserver.net/web';
    case 'st':
      return 'https://cache-st.myserver.net/web';
    case 'dev':
      return 'https://cache-dev.myserver.net/web';
    default:
      return '';
  }
};
const namespace = process.env.NAMESPACE;

__webpack_public_path__ = `${assetPrefixForNamespace(namespace)}/`;

file.js

import png from './image.png';

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.(png|jpg|gif)$/i,
        loader: 'file-loader',
        options: {
          name: '[name].[contenthash].[ext]',
          outputPath: 'static/assets/',
          publicPath: 'static/assets/',
          postTransformPublicPath: (p) => `__webpack_public_path__ + ${p}`,
        },
      },
    ],
  },
};

Result when run with NAMESPACE=prod env variable:

# result
https://cache.myserver.net/web/static/assets/image.somehash.png

Result when run with NAMESPACE=dev env variable:

# result
https://cache-dev.myserver.net/web/static/assets/image.somehash.png

Contributing

Please take a moment to read our contributing guidelines if you haven't yet done so.

CONTRIBUTING

License

MIT