# GeoPattern — Examples

> Hands-on walkthroughs with GeoPattern: generate a pattern from a seed, set type and color in custom mode, use it as a CSS background, and build a per-user pattern.

Source: https://www.jpkc.com/db/en/tools/geopattern/examples/

Back to the overview: [GeoPattern](https://www.jpkc.com/db/en/tools/geopattern/) · Open the tool: [www.jpkc.com/tools/geopattern/](https://www.jpkc.com/tools/geopattern/)

The [manual](https://www.jpkc.com/db/en/tools/geopattern/manual/) explains every option and pattern type in detail. This page adds **concrete workflows**: typical tasks played through step by step. The interface is in English, so field and button names appear verbatim.

## Example 1: Your first pattern from a seed

The starting point — you want to see how text becomes a pattern.

1. Open [GeoPattern](https://www.jpkc.com/tools/geopattern/). The **Input String** field already contains `GitHub`, and the preview shows the pattern generated from it.
2. Replace the text with your own seed — your name or a domain, say — and press **Enter** (or click **Generate Pattern**). The preview changes instantly.
3. **Notice the principle:** the `Use custom pattern & color` switch is off — so your text alone determines both the pattern type and the color. The badge in the top right of the preview names the hex value used.
4. Type the same text again: an identical pattern. Change a single character: a completely different pattern. That's the deterministic logic — no randomness.

In seconds you have a reproducible graphic without designing anything.

## Example 2: Same seed, different color — custom mode

You like the shape but need a color that fits your brand.

1. Leave your seed in the **Input String** field.
2. Turn on the **Use custom pattern & color** switch. The `Pattern Type` and `Custom Color` fields become usable.
3. Click into **Custom Color** and pick a hex value in the Coloris picker — one of your brand colors or one of the eight swatches. The preview updates immediately.
4. **Read the result:** the basic arrangement stays — it still comes from the seed — but the color is now yours. The badge shows exactly the value you chose, which also lands in the export.

This decouples recognizability (seed) from coloring (brand).

## Example 3: Forcing a specific pattern type

Sometimes you want hexagons or triangles specifically, regardless of which type the hash would have picked.

1. Turn on **Use custom pattern & color**.
2. Open **Pattern Type** and pick one of the 16 types, e.g. `Hexagons` or `Triangles`. The preview jumps to the chosen type at once.
3. Try the types out — `Sine Waves` for a wavy line look, `Plaid` for a tartan feel, `Concentric Circles` for rings. The seed still determines the specific expression within the type.
4. Combine this with a **Custom Color** from Example 2 until look and color are right.

## Example 4: Embedding as a CSS `background-image`

The most common goal — you want the pattern in a page without a separate image file.

1. Generate your pattern (seed, optionally type/color in custom mode).
2. Expand the **Base64 Data URLs** area at the bottom and click **Copy** on **SVG Data URL**. You now have a `data:image/svg+xml;…` string on the clipboard.
3. Drop it into your CSS:

   ```css
   .hero {
   	background-image: url("data:image/svg+xml;…");
   	background-repeat: repeat;
   }
   ```

4. Because SVG is a vector, the pattern tiles cleanly and stays sharp at any screen size — and there's **no extra HTTP request**, because the image lives inside the stylesheet.

If you need a raster image instead (for an email or an old system), copy the **PNG Data URL** or use **Save PNG**.

## Example 5: A unique pattern per user (avatars/banners)

The classic GitHub use case — every account should automatically get its own graphic.

1. Leave the **Use custom pattern & color** switch **off** so that type and color come purely from the seed.
2. Enter a stable identifier per user as the **Input String** — a username, email address, or ID.
3. **Generate Pattern** — and you have a unique, recognizable graphic for exactly that identifier.
4. Repeat for further identifiers: each gets its own pattern, and because the logic is deterministic, the same identifier will later look exactly the same again.
5. Export per user with **Save SVG** or **Save PNG**; the file name automatically takes the seed (`alice.svg`, `bob.svg`).

## Example 6: Choosing SVG vs. PNG deliberately

Both formats have their place — here's how to decide.

1. Generate your pattern.
2. **Save SVG** when you need lossless scalability: as a CSS background, for large surfaces, or when the file will later vary in size. The file is small and sharp at any resolution.
3. **Save PNG** when the target can't handle SVG: certain email clients, social media uploads, or legacy software. Bear in mind: the PNG is fixed to its rasterized size and won't scale losslessly.
4. For a quick file-less embed, take the matching **Data URL** from the `Base64 Data URLs` area instead.

---

There's more depth on the other pages: the [overview](https://www.jpkc.com/db/en/tools/geopattern/) for the big picture, the [manual](https://www.jpkc.com/db/en/tools/geopattern/manual/) for every option in detail, and the [tips & tricks](https://www.jpkc.com/db/en/tools/geopattern/tips/) for pitfalls and combinations. You can try all of this directly in the [tool](https://www.jpkc.com/tools/geopattern/).