Course contentsShow
← JavaScript
Lesson 2007 of 2,72341. Modern JavaScript Features (ES2020+)Free lesson

When to Use structuredClone

Practical scenarios where deep cloning is necessary and when shallow copies or immutability patterns suffice.

When to Use structuredClone

You'll learn when deep cloning is actually necessary and when simpler alternatives are better choices.

Now that you know structuredClone exists, the real question is: when should you actually use it? Deep cloning is powerful but has a performance cost. Many situations don't require it at all.

When You Need structuredClone

Use structuredClone when you must truly duplicate nested structures without any shared references:

  • State snapshots for undo/redo systems where history must be fully independent
  • Passing data to Web Workers (especially with the transfer option)
  • Cloning complex configuration objects that will be modified in different contexts
  • Creating test fixtures where each test needs pristine, unshared data
// Undo system: each snapshot must be completely independent
const stateHistory = [];
stateHistory.push(structuredClone(currentState));

When Shallow Copies Suffice

Use the spread operator or Object.assign when you only need to clone the top level:

// Top-level properties are primitive or won't be mutated
const userCopy = { ...user };

When Immutability Patterns Are Better

If you're working with frameworks like React or Redux, immutable updates are often cleaner and more performant than cloning:

// Better: create new object with updated property
const updated = { ...state, count: state.count + 1 };

Think Cost vs. Benefit

structuredClone walks the entire object tree. For small objects, it's negligible. For massive nested structures, it can be expensive. Ask: do I really need complete independence, or can I manage references carefully?

Key Takeaway: Use structuredClone when you need truly independent nested copies; prefer shallow copies or immutable update patterns when references won't cause problems.