Bulk Fix

Fix all instances of a finding at once instead of clicking through nodes one by one

Pro feature. See pricing.

Bulk Fix lets you apply the same fix to every node in a grouped finding with one click. Instead of fixing 47 orphaned fills individually, you fix them all at once.

When to use Bulk Fix

Use Bulk Fix when LintKit groups multiple nodes under a single finding. This happens most often with:

• Orphaned fills or strokes that share the same color
• Fractional pixel values across many layers
• Spacing violations that all snap to the same target
• Cleanup operations like removing hidden layers

Use individual fixes when you want to review each node before changing it, or when different nodes in the same group need different fixes.

How to apply a bulk fix

1. Scan your file

   Run a scan from the Overview tab. LintKit groups findings that share the same root cause.

2. Open a grouped finding

   Click a finding that shows a node count (for example, “47 layers”). This expands the finding to show the affected nodes and available fixes.

3. Choose a fix

   Select the fix you want to apply. For orphaned fills, this might be “Map to style” with a specific style name. For fractional pixels, it might be “Snap to pixel.”

4. Click Fix all

   Click Fix all to apply the chosen fix to every affected node. If more than 10 nodes are affected, LintKit shows a confirmation dialog so you can review the scope before proceeding.

5. Review the results

   LintKit processes nodes in batches and reports the outcome. If any nodes failed, you will see which ones and why.

Supported finding types

Bulk Fix works with any finding that groups multiple nodes and has an auto-fixable suggestion:

Finding type	Bulk Fix action
Orphaned fills, strokes, text, effects, grids	Map all matching nodes to the same style or variable
Fractional pixels	Snap all sub-pixel values to whole integers
Spacing violations	Snap all off-scale values to the nearest allowed value
Radius normalization	Normalize all values to the allowed set
Stroke weight normalization	Normalize all weights to the allowed set
Cleanup (hidden layers, empty groups, empty frames)	Remove all matching nodes
Cleanup (single-child groups)	Flatten all matching groups

Batch processing

LintKit processes nodes in batches of 50. This prevents the plugin from freezing Figma’s UI, even when fixing hundreds of nodes. You will see progress as each batch completes.

Confirmation dialog

When a bulk fix affects more than 10 nodes, LintKit shows a confirmation dialog before proceeding. The dialog tells you:

• How many nodes will be changed
• What fix will be applied
• A prompt to confirm or cancel

This gives you a chance to reconsider before making a large change.

Undo behavior

Each fix is a separate undo step in Figma’s history. Bulk Fix does not undo as a single batch. If you bulk-fix 47 nodes and want to undo all of them, you need to press Cmd+Z (Mac) or Ctrl+Z (Windows) 47 times. Consider this before applying large bulk fixes.

Error handling

If some nodes cannot be fixed — for example, because they were deleted, locked, or moved during the operation — LintKit reports which nodes failed and why. Successfully fixed nodes are not rolled back.

Possible failure reasons include:

• Node was removed before the fix reached it
• Node is locked
• The target style or variable no longer exists
• Permission denied

LintKit shows up to 10 error samples in the failure report.

Free tier behavior

The free tier’s 5 fixes per session limit applies within Bulk Fix. Each node fixed counts as one fix toward your session cap. If you start a bulk fix with 47 nodes and have 3 fixes remaining, LintKit will fix 3 nodes and stop. Upgrade to Pro for unlimited fixes, or close and reopen the plugin to reset your session counter.