Randomize Shape changes the blob’s unsigned 32-bit seed, and that seed drives the path while your vertex count, irregularity, canvas size, and fill color stay unchanged.

That behavior is intentional in the SVG Blob Generator: the seed is the only randomized input, while the SVG path is generated output. Pressing the button asks the browser’s cryptographic random source for a new seed. It does not reroll the color, dimensions, or explicit geometry controls.

why does randomize change only the seed when i generate svg blob
Why Does Randomize Change Only the Seed for SVG Blobs?

What “change only the seed” actually means

The wording describes the state of the controls, not every part of the final drawing. When you press Randomize Shape, the displayed unsigned 32-bit seed is replaced. The generator then combines that new value with your existing settings to calculate new vertex radii and new path data. Your chosen number of vertices, irregularity percentage, canvas size, and HEX fill are not randomized by that action.

Action Seed Generated path Explicit settings
Generate a blob Uses the current displayed seed Derived from the seed and geometric controls Remain under your control
Press Randomize Shape Replaced with a new seed Regenerated from the new seed Remain unchanged
Experience an unrelated rerender Stays unchanged Stays unchanged Stay unchanged
Repeat the same recipe Uses the same recorded seed Produces the same path and markup Must also be the same

The seed is therefore not an inert label attached after drawing. It is the one variable input that selects among deterministic shape outcomes. The path is the consequence, while the visible controls remain your constraints.

Why the outline changes without moving the controls

Vertex positions begin at equal angular intervals around the canvas center. Irregularity determines how far each vertex sits from that center through a seeded radius generator. A new seed can assign different radii, so the curved outline changes even though none of the sliders or fields moves. The generator starts at the midpoint between the last and first vertices, then joins successive midpoints with quadratic Bézier curves controlled by the original vertices.

That construction produces a smooth, closed vector outline. Its move, quadratic-curve, and close commands follow the path grammar documented by the W3C SVG 2 Paths specification and MDN’s SVG path reference. Those references describe SVG path syntax; the seeded radius model is the generator’s own deterministic behavior.

At zero percent irregularity, every vertex receives the same radius, so pressing Randomize can leave the visible silhouette effectively unchanged even though the seed changes. Raising irregularity enables radial variation. More vertices can make the silhouette more detailed, but they do not increase the precision of the serialized coordinates.

The controls that remain in charge

The seed operates within a fixed set of design inputs rather than replacing them.

Setting Accepted value Role in the result
Vertex count Integers from three through twelve Sets the number of evenly spaced vertices
Irregularity Zero through one hundred percent Controls the amount of seeded radial variation
Canvas size Three practical presets in the interface; integers from 128 through 1024 are accepted in the tested generator logic Sets the square width, height, and matching viewBox
Fill A strict six-digit HEX color Sets the blob’s solid fill
Seed An unsigned 32-bit value Selects the deterministic radius assignment

Invalid values are rejected by the generator instead of being silently clamped. The browser color control supplies a valid value during normal interaction, while the size interface presents three practical presets.

How to generate and reproduce an SVG blob

  1. Set the fixed design inputs. Choose three to twelve vertices, set irregularity from zero through one hundred percent, select a square size, and choose a strict six-digit HEX fill. Confirm the selected size in the exported width and height, because the on-page preview may be constrained by the page layout.
  2. Press Randomize Shape when you want another candidate. The browser supplies a new seed at that moment, and the preview updates immediately. Continue randomizing until the silhouette fits your design. At zero percent irregularity, raise the irregularity first if you expect visible changes between candidates.
  3. Record the complete recipe. Save the displayed seed together with the vertex count, irregularity, canvas size, and fill color. A seed alone cannot reproduce the same blob when those other inputs differ.
  4. Copy the SVG markup or download the vector file. Copy SVG writes the complete markup to the clipboard; if clipboard permission is denied, the same markup remains available in a read-only text area for manual selection. The download uses a filename containing the seed and remains genuine SVG text encoded as a data URL.
  5. Test the result in its destination. Open the copied or downloaded blob in the final browser, editor, email client, or content system. Some sanitizers restrict inline SVG or data URLs even when the underlying markup is valid.

If the new outline is unsuitable, the SVG Blob troubleshooting checklist can help separate a geometry problem from an export or destination problem.

Why rerendering does not create another random blob

Randomness is requested only when Randomize Shape is pressed. It is not called during React rendering, so hydration and unrelated rerenders cannot silently replace the seed or alter the graphic. An ordinary component update therefore does not behave like another press of the randomize button.

Equal settings and the same seed produce the same points, path data, and complete SVG markup. Coordinates are rounded to two decimal places during serialization, which keeps the output readable and stable while retaining ample precision for the available canvas sizes.

The exported SVG is static vector geometry, not a live seed-driven generator. It contains one path and no metadata, while the downloaded filename includes the seed. Adding or changing a seed string inside copied markup will not redraw the shape. To alter the geometry, return to the generator, change the seed or another input, and export the result again.

What to verify before reusing the blob

Inspect the preview at both large and small sizes. High irregularity can create tight bends or an unbalanced visual mass, and the silhouette may behave differently over text or other detailed content. If the blob will sit behind text, check the actual color contrast and leave enough padding; the SVG’s internal canvas margin does not guarantee readability.

  • Confirm that the exported width and height match the selected canvas size and that the viewBox matches those dimensions.
  • Check the accessible image label, the single SVG path, and the strict six-digit HEX fill in the output.
  • Expect simple geometry rather than a full vector-editing result. The generator does not add gradients, strokes, shadows, clipping paths, animation, CSS classes, metadata, optimization passes, or raster fallbacks.
  • Add any required styling later in a compatible vector editor, then test the revised file again in the destination application.
  • Verify that the blob remains vector geometry when resized in a compatible editor or browser; the download is not a screenshot.

No shape, color, seed, or exported markup is uploaded, and no account or external graphics service is required. The download also does not create a persistent server file. Its behavior inside a particular site still depends on that destination’s security rules, so a successful preview in the generator is not a substitute for testing the final file where it will be used.

When unchanged controls are the expected result

The apparent behavior is correct: Randomize replaces only the seed because the generator is designed to preserve explicit design choices. The outline normally changes because the seeded radii and derived path are recalculated from that new value. To change the fill color without changing the geometry, edit the fill separately. To change the silhouette while preserving the style, press Randomize Shape and save the new seed with the rest of the recipe. If the result still looks wrong, compare the complete settings and test the static SVG in its target application rather than expecting an embedded seed to update it.

Related reading: Why Does CSS Use a Data URL When Generating SVG Patterns?.