Skip to content


The Randomizer interface allows you to use a custom randomness source within Faker.


Faker's default Randomizer is sufficient in most cases. Change this only if you want to use it to achieve a specific goal, such as sharing the same random generator with other instances/tools.

There are two connected use cases we have considered where this might be needed:

  1. Re-Use of the same Randomizer within multiple Faker instances.
  2. The use of a random number generator from a third party library.

Built-In Randomizers

Faker ships with two variations

import {
  generateMersenne32Randomizer, // Default prior to v9
  generateMersenne53Randomizer, // Default since v9
} from '@faker-js/faker';

const randomizer = generateMersenne53Randomizer();

The 32bit Randomizer is faster, but the 53bit Randomizer generates better random values (with significantly fewer duplicates).

But you can also implement your own by implementing the related interface.

Using Randomizers

A Randomizer has to be set during construction of the instance:

import { Faker, Randomizer } from '@faker-js/faker';

const customFaker = new Faker({
  locale: ...,
  randomizer: ...,

The following methods take a Randomizer as argument:

Re-Using a Randomizer

Sometimes it might be required to generate values in two different locales. E.g. a Chinese person might have an English identity to simplify the communication with foreigners. While this could also be achieved with two independent Faker instances like this:

import { fakerEN, fakerZH_TW } from '@faker-js/faker';


const firstName = fakerZH_TW.person.firstName(); // 炫明
const alias = fakerEN.person.firstName(); // Arthur

There might be issues regarding reproducibility, when seeding only one of them.

By sharing a Randomizer between the two instances, you omit this issue by affecting all instances simultaneously.


This gets more important if the seeding happens at a different location than the data generation (e.g. due to nesting).

import { en, Faker, Randomizer, zh_TW } from '@faker-js/faker';

const randomizer: Randomizer = ...;

const customFakerEN = new Faker({
  locale: en,

const customFakerZH_TW = new Faker({
  locale: [zh_TW, en],

// customFakerEN.seed(5); // Redundant
// customFakerZH_TW.seed(5); // Redundant

const firstName = fakerZH_TW.person.firstName(); // 炫明
const alias = fakerEN.person.firstName(); // John (different from before, because it is now the second call)

This is also relevant when trying to use faker's random number generator in third party libraries. E.g. some libraries that can generate strings from a RegExp can be customized with a custom random number generator as well, and since they will be used in the same context it makes sense to rely on the same randomness source to ensure the values are reproducible.

Third-Party Randomizers

Sometimes you might want to use a custom/third-party random number generator. This can be achieved by implementing your own Randomizer and passing it to supported methods.


Faker does not ship Randomizers for third-party libraries and does not provide support for bridging the gap between libraries. The following examples show how the interface can be implemented, but they are not tested for correctness. Feel free to submit more Randomizer examples for other popular packages.


The following is an example for a pure-rand based Randomizer:

import { Faker, Randomizer, SimpleFaker } from '@faker-js/faker';
import { RandomGenerator, xoroshiro128plus } from 'pure-rand';

export function generatePureRandRandomizer(
  seed: number | number[] = ^ (Math.random() * 0x100000000),
  factory: (seed: number) => RandomGenerator = xoroshiro128plus
): Randomizer {
  const self = {
    next: () => (self.generator.unsafeNext() >>> 0) / 0x100000000,
    seed: (seed: number | number[]) => {
      self.generator = factory(typeof seed === 'number' ? seed : seed[0]);
  } as Randomizer & { generator: RandomGenerator };
  return self;

Released under the MIT License.