Browser Extensions Development (Chrome & Edge) · Lesson

Understanding Manifest V3 Structure

Explore the manifest.json file in depth, learning about required fields and common configurations for Manifest V3.

Understanding Manifest V3 Structure is a free Browser Extensions Development (Chrome & Edge) lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Browser Extensions Development (Chrome & Edge) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

The Blueprint of Your Extension

Every browser extension starts with a core configuration file called manifest.json. Think of it as the blueprint or identity card for your extension.

This file tells the browser everything it needs to know: its name, version, what permissions it needs, and which files make up its different parts.

Introducing Manifest V3

Manifest V3 is the latest version of the extension platform, bringing significant changes focused on security, privacy, and performance.

All new extensions must use Manifest V3, and existing extensions are migrating. Understanding its structure is crucial for modern extension development.

Required Field: manifest_version

The manifest_version field is mandatory and tells the browser which set of APIs and security features your extension expects.

For Manifest V3, this value must always be 3.
It's the very first declaration in your manifest.json file.

Required Fields: name and version

These two fields are also essential for every extension:

name: This is the user-visible name of your extension. It appears in the browser's extension management page and in the web store.
version: This specifies the version of your extension, typically following semantic versioning (e.g., "1.0.0"). It helps users track updates.

Your First Manifest File

Let's see the absolute minimum needed for a valid Manifest V3 file. This simple JSON structure is the foundation for any extension you build.

{
  "manifest_version": 3,
  "name": "My Basic Extension",
  "version": "1.0"
}

Optional Field: description

While not strictly required, adding a description is highly recommended. It provides a short summary of what your extension does.

This description is visible to users in the browser's extension management page and is crucial for your listing in the Chrome Web Store or Edge Add-ons store.

Optional Field: icons

The icons field allows you to define images that represent your extension. Browsers use different sizes for various UI contexts:

Toolbar buttons (16x16, 24x24, 32x32 pixels)
Extension management page (48x48 pixels)
Web store listing (128x128 pixels)

Always provide a 128x128 icon for store listings.

Optional Field: action

The action field defines the behavior of your extension's toolbar button, often called the 'browser action' button. This is the icon next to the address bar.

It commonly points to an HTML file (a "popup") that appears when the button is clicked, allowing for quick user interaction with your extension's UI.

A More Detailed Manifest

Let's expand our manifest to include a description, icons, and an action popup. This gives your extension a clear identity and a basic interactive element.

{
  "manifest_version": 3,
  "name": "My Awesome Extension",
  "version": "1.0",
  "description": "A simple extension to do awesome things!",
  "icons": {
    "16": "icons/icon16.png",
    "48": "icons/icon48.png",
    "128": "icons/icon128.png"
  },
  "action": {
    "default_popup": "popup.html",
    "default_icon": {
      "16": "icons/icon16.png",
      "24": "icons/icon24.png",
      "32": "icons/icon32.png"
    },
    "default_title": "Click to open!"
  }
}

Quick Check on Manifest Fields

Based on what you've learned, identify the fields that are absolutely required in a Manifest V3 manifest.json file.

Manifest V3: Your Extension's Identity

We've explored the fundamental role of the manifest.json file, understanding it as the blueprint for your browser extension.

You learned about the three critical required fields: manifest_version (always 3), name, and version.
We also touched upon important optional fields like description, icons, and action, which define your extension's appearance and basic user interface.

Mastering the manifest file is the first step to building powerful and compliant browser extensions!

Frequently asked questions

Is the “Understanding Manifest V3 Structure” lesson free?

Yes — the full text of “Understanding Manifest V3 Structure” is free to read here on the web, and the Browser Extensions Development (Chrome & Edge) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Browser Extensions Development (Chrome & Edge) course, upgrade to CoddyKit PRO.

What will I learn in “Understanding Manifest V3 Structure”?

Explore the manifest.json file in depth, learning about required fields and common configurations for Manifest V3. You practise Browser Extensions Development (Chrome & Edge) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Browser Extensions Development (Chrome & Edge)?

No prior experience is required. Browser Extensions Development (Chrome & Edge) on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Understanding Manifest V3 Structure” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Browser Extensions Development (Chrome & Edge) lesson?

Yes. Every Browser Extensions Development (Chrome & Edge) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Browser Extensions Development (Chrome & Edge)