Migrate from v3.x

From v3.x, the biggest migration risk is usually options compatibility.

Priority changes

• particles.color moved to particles.paint.fill.
• particles.stroke moved to particles.paint.stroke.
• New palette-centric flows can populate paint values automatically.

If colors look wrong after upgrade, check those keys first.

Option mapping examples

Before (v3.x style):

const options = {
  particles: {
    color: {
      value: "#ff0000",
    },
    stroke: {
      width: 2,
      color: "#000000",
    },
  },
};

After (current):

const options = {
  particles: {
    paint: {
      fill: {
        value: "#ff0000",
      },
      stroke: {
        width: 2,
        color: "#000000",
      },
    },
  },
};

Load API note

Current API uses a single params object:

await tsParticles.load({
  id: "tsparticles",
  options,
});

If your v3.x project still contains legacy positional calls from older snippets, migrate them now.

Before (legacy positional):

await tsParticles.load("tsparticles", options);

After (object params):

await tsParticles.load({
  id: "tsparticles",
  options,
});

Recommended steps

1. Align all @tsparticles/* packages to the same latest version line.
2. Replace deprecated option keys (particles.color, particles.stroke) with particles.paint.*.
3. Verify custom plugins/shapes are loaded before tsParticles.load(...).
4. Re-test interactions and performance-sensitive scenes.

Checklist

• Keep one version line across engine, bundles, wrappers, presets, and plugins.
• Replace deprecated imports with package-level imports when needed.
• Validate SSR wrappers (Next/Nuxt) still initialize only on client side.

Useful option docs

• Option rename matrix: /guide/option-rename-matrix
• particles.paint: /options/particles-paint
• particles.color migration note: /options/particles-color
• particles.stroke migration note: /options/particles-stroke

References

• Versioning notes: /releases/
• Root repository releases: https://github.com/tsparticles/tsparticles/releases