Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Next.js Chrome Extension Starter example application that demonstrates how to build a Chrome extension using Next.js, React, and Node.js.

A full-stack Next.js TypeScript template focused on functionality over UI, featuring Zustand, TanStack Query, and ESLint 9 support.
Next.js Chrome Extension Starter is a demo boilerplate for building a Chrome extension with Next.js, React, and Node.js, and it produces a static export that loads directly into Chrome as an unpacked extension.
Next.js Chrome Extension Starter is an example application that demonstrates how to combine a Next.js front end with the Chrome extension platform. It takes a standard Next.js multi-page app as input and, through the build and export pipeline, outputs a static 'out' folder that Chrome can load as an unpacked extension. The project was created by Justinas Kairys (ibnzUK), is published on GitHub under the MIT License, and has received 217 stars.
npm run build triggers prep and export commands that create the 'out' folder and rename '_next' to 'next' so Chrome accepts the extension's assets.npm run dev serves the app at http://localhost:3000, allowing normal Next.js development before building the extension.After cloning the repository, run npm install to install dependencies. To develop, run npm run dev and open http://localhost:3000. To create the extension, run npm run build; this runs the prep and export scripts to generate an 'out' folder with the '_next' directory renamed to 'next'. In Chrome, go to chrome://extensions, enable Developer mode, click "Load Unpacked", and choose that out folder.
Yes, the project is open source and distributed under the MIT License, so you can use, modify, and redistribute it freely as long as you preserve the copyright notice.
Follow the README steps: run npm run build, open chrome://extensions, enable Developer mode, click "Load Unpacked", and select the out folder generated by the build. The extension then appears in your browser.
npm run build runs the prep and export scripts, creating a static 'out' folder. It also renames the '_next' directory to 'next'; this rename is necessary because Chrome's extension loader does not accept the underscore prefix.
The README describes a demo application with multiple pages; it does not mention specific Chrome extension features like content scripts or background workers. The focus is on the Next.js UI integration.
The content does not specify a Manifest V2 or V3 version, but the load-unpacked workflow described works with the current Chrome extension loading mechanism.