Digital badges have moved from novelty to necessity. From workforce development programs to university micro-credentials to corporate training completions, a well-designed digital badge is a professional asset that earners carry on LinkedIn, resumes, and email signatures for years. But what goes into making one that actually works, visually, technically, and credentially?
This guide walks you through the entire process of designing a digital badge from scratch: establishing your concept, making the right visual decisions, choosing your tools, exporting correctly, and embedding the metadata that turns a plain image into a verifiable credential. Whether you're a solo instructor, an HR manager, or running a multi-department credentialing program, these steps apply.
Before you open a design tool, it helps to understand what a digital badge actually is. On the surface, it's a PNG image, usually square, usually colorful. But under the hood, a compliant digital badge carries structured metadata according to the Open Badges specification (now IMS Global Open Badges v3.0). That metadata includes:
When this data is embedded directly into the PNG file, it's called a baked badge. When it lives on a hosted platform and the image links to it, it's a hosted badge. Either way, the image design and the metadata must work together.
Before touching any design tool, answer three questions clearly:
These answers drive every visual decision you'll make. A beginner badge and an expert-level badge should look different, and the criteria you define here will be embedded in the metadata later.
Your choice of tool depends on your skill level and workflow:
For this guide, we'll describe the process in tool-agnostic terms so you can apply it wherever you work.
Even if you're designing a single badge, you're planting the seeds of a badge system. Establish these elements before you draw anything:
Set your canvas to 600×600 pixels (or larger if you want room to scale down). Work in square format. Here's a proven layout structure:
Design tip: zoom out to 60×60 pixels and check legibility. Badges are frequently displayed at thumbnail size on LinkedIn and email signatures. If your badge looks muddy at that scale, simplify.
Export your badge as a PNG with transparency. Specifications:
Avoid JPEG for badges, compression artifacts degrade edges and text. SVG is sometimes used for display but cannot carry baked Open Badge metadata.
This is the step that turns your PNG into a verifiable credential. Open Badge metadata is structured JSON-LD data attached to the image. The key fields are:
If you're using a platform like IssueBadge.com, this data is generated and embedded automatically when you issue the badge. If you're doing it manually, tools like Badgr or the Open Badge Factory can handle baking.
Before issuing to anyone, validate your badge:
Once validated, you're ready to issue. On IssueBadge.com you can issue directly from the platform and send earners a notification with their acceptance link.
Badges operate in a unique design space. Unlike a poster or website, a badge must communicate clearly at sizes ranging from 30×30 pixels (favicon-sized thumbnails) up to 300×300 pixels on a profile page. This demands a level of visual economy that most design tasks don't require.
Dark backgrounds with light icons or light backgrounds with dark icons always read better than mid-tone combinations. Avoid using two colors with similar luminance (e.g., medium blue on medium green).
Two to three colors is the sweet spot. A primary badge color, a secondary accent, and white or black for text and fine detail. More colors create visual noise and look amateur at small sizes.
Texture and gradient backgrounds can look impressive at full size but turn into mud at thumbnail scale. If you want depth, use a single subtle gradient rather than a pattern or photograph.
Your central icon should occupy at least 40% of the badge's interior area. It should be recognizable in silhouette alone. If someone can't tell what it is with the color removed, redesign it.
If you're designing more than one badge, you're building a family. A well-designed badge family has shared DNA, consistent shapes, typography, and structural layout, but clear differentiation between levels or categories through color and iconography.
A practical approach: design one master badge template with locked structural elements (border shape, font, issuer mark placement) and variable elements (color fill, central icon, badge name). This lets you produce a consistent family quickly and maintain visual coherence as your program grows.
Learn more about structuring a full program in our guide on how to build a badge program for your organization.
Here's a practical comparison to help you choose:
A digital badge image should be at least 600×600 pixels, exported as a square PNG. The Open Badges specification does not mandate a specific pixel size, but 600×600 ensures sharpness on high-resolution displays and social platforms.
Not necessarily. Platforms like IssueBadge.com include built-in badge builders with templates, so you can produce professional results without graphic design experience. However, custom vector work in tools like Illustrator gives you maximum control.
PNG is the standard format for digital badges because it supports transparency and can carry embedded Open Badge metadata as a baked badge.
A baked badge is a PNG image file that has Open Badge assertion data embedded directly inside it. When someone shares the image, the metadata travels with it and can be extracted by any compliant verifier.
A simple badge using a template can be ready in under an hour. A fully custom-designed badge with original iconography and brand guidelines typically takes two to four hours of design work.