Adding a Dotted World Map to Confluence Pages

Adding a dotted world map to a Confluence page is a quick way to give a team wiki some visual context — office locations, remote-team distribution, or market coverage — without pulling engineering time into building a custom macro. Confluence handles image uploads natively, and a dotted map's flat, low-file-size style fits the format well.

Company wikis tend to have a handful of pages that benefit from a map: a "Where We Are" page for new hires, an internal directory of regional offices, or a status page describing which markets a product supports. These pages get revisited constantly, so the map needs to be easy to update, not just easy to add once.

Uploading the Map

Confluence supports both PNG and SVG uploads through its standard image insertion, though rendering behavior for SVG can vary depending on your Confluence version and whether you're on Cloud or Data Center. The safer default across both:

1. Export your map as a PNG with a transparent background — this renders identically across every Confluence version and theme
2. On your page, use Insert > Files and images (or drag-and-drop directly into the editor)
3. Click the inserted image to open sizing options — Confluence lets you set it to a percentage of page width or a fixed pixel size
4. Add alt text describing what the map shows (e.g., "Map showing our six regional offices") — this matters for accessibility and also helps the image show up sensibly in Confluence's search indexing

If your instance does render SVG cleanly, it's worth using it for a page that needs to look sharp at multiple screen sizes, since teams view Confluence on everything from ultrawide monitors to tablets.

Where a Map Fits on a Wiki Page

• Onboarding / "Where We Are" pages — a simple world map with markers or highlighted countries next to a short list of office addresses
• Distributed-team pages — a map showing where team members are based, often paired with a time-zone table
• Product or market-availability pages — a map highlighting which countries a product, feature, or support tier is available in
• Status or infrastructure pages — a map of server or data-center regions, similar in spirit to how status pages present coverage externally

That last case overlaps with how companies build external-facing infrastructure pages — see designing server location graphics for status pages for layout ideas that translate well to an internal Confluence version.

Keeping the Map Current

The biggest practical issue with maps on wiki pages isn't the design — it's staleness. A map showing five offices is wrong the day a sixth office opens, and nobody remembers to regenerate it. A few habits help:

• Note the source settings in a comment on the page (region, highlighted countries, color) so whoever updates it later doesn't have to guess
• Link the map to the source list — if the page also has a text list of offices or team locations, keep that list as the source of truth and treat the map as illustrative rather than authoritative
• Assign it to a page owner as part of your normal wiki-maintenance review, the same way you'd flag any other page that goes stale

Formatting Considerations

Confluence pages are read at a range of widths depending on whether someone's viewing in the sidebar-collapsed reading mode or a narrower embedded panel. A few adjustments help the map hold up:

• Keep dot density moderate — a very high-density map can look muddy when Confluence scales it down for a narrower viewport
• Use a background that works in both Confluence's light theme and dark theme if your workspace has dark mode enabled, since a white-background PNG will show a hard box in a dark UI
• If the map anchors a specific section (like a regional-office table), place it directly above or beside that section rather than at the top of an unrelated page, so the two stay visually connected

A Simpler Alternative for Some Teams

Some teams use Confluence primarily as an internal home base but link out to a public-facing page for the canonical version of team or office information. If that's your setup, it may be worth building the primary map for an interactive office locations page or your remote-team website page first, then reusing the same exported image inside Confluence — one source asset, two destinations.

Quick Checklist

• Export PNG with transparent background for the most consistent rendering across Confluence versions and themes
• Add descriptive alt text for accessibility and search
• Note your generator settings somewhere so updates are quick, not a redo
• Assign an owner so the map doesn't quietly go stale

Generate the Map

Set your region and highlighted locations in the map generator, export a PNG, and drop it into your Confluence page. If your wiki also tracks where your team works day to day, see visualizing remote team locations with dotted maps for design ideas that translate directly to an internal page.