Skip to content


Supercharge frame development with Frog's built-in devtools

When developing Frames, it's useful to get feedback in real-time. Shortening the dev loop helps you iterate on your Frames and launch them faster.

Frog includes built-in devtools that include a live preview of your frame, time-travel debugging, request information, validation, and more to help with development.

Getting Started

Once you've set up your Frog project, you can attach the devtools to your frames by adding the devtools function to your app. No need to install anything else or clone a separate repo!

import { devtools } from 'frog/dev'
import { serveStatic } from 'frog/serve-static'
export const app = new Frog()
app.frame('/', (c) => { ... })
devtools(app, { serveStatic })

Next, you can start a dev server for your frames by running the following command:

frog dev

This will start a dev server at http://localhost:5173. Then you can head to the /dev route (http://localhost:5173/dev) to see a live preview (with live reloading) of your frames.

To learn more about frog dev checkout the dev command docs.


The best way to learn about what features are included in the Frog Devtools is to try them out yourself! For those that haven't tried out Frog yet, here's a brief overview of what's included.

Live Reload

When you make changes to and save your Frame, the devtools will automatically reload your Frame, while maintaining the current state. This makes it easy to see how your changes affect the Frame and allow you to iterate quickly on nitpicky details, like getting your Frame image just right.

Browser URL State

The Frog Devtools keep track of all its state in the URL via a query hash. This means that you can share a link to the devtools with someone else and they'll see the same state as you. This is useful for sharing bugs, or for getting feedback from others.

Frame Preview

The Frame Preview allows you to interact with your Frame, just like you would in production. Click buttons, add text, and see how your Frame responds to user input.

Sign In With Farcaster

You can connect your Farcaster account to the devtools to test verification with your Frame. Simply, scan the QR code or copy-paste the login code in your mobile browser to sign in. You can also impersonate other users by entering a custom FID.

Request Timeline

See all the requests made by your Frame and switch between them to see differences in the Frame, validation, state, metrics, and more. This is useful for restoring previous states, debugging errors, and profiling performance between different Frames.


Every Frame is an app. The navigator allows you to switch between different Frames that exist in your Frog app. It also allows you to navigator forward and backward (like you can do in your browser for web apps), as well as refresh the current Frame.


Getting your Frame right is important. Frog manages most of the internals for you, but there are still some areas where you can make mistakes. The devtools will show you any validation errors for your Frame as well as some info on how to fix them.

Dev Panel

Lastly, the dev panel is where you can see information for the current Frame, like specifics about the Frame's request, context value, current and previous state, and underlying meta tags powering your Frame.


For each Frame request, Frog breaks down metrics related to your Frame, including request speed, Frame document size, and Frame image size. These are important metrics to pay attention to when developing Frames as they affect how users experience your Frames.

Standalone Mode

The Frog Devtools work best when used with Frog Frames, but you can also use the devtools with non-Frog Frames. There are two methods: global install and executable.

The global installation method is recommended as it works offline without an Internet connection.

Global Install

First, install frog globally with your package manager:

npm i -g frog

Then, run the frog command to start the dev server:

[running] frog@v0.7.5
  Local:   http://localhost:5173/
  Network: use --host to expose

A local dev server will start, where you can test your frames. For more information on command options, check out the frog command docs.


You can execute directly via npx, pnpx, or bunx:

npx frog


Your experience using Frog's Devtools is important! Please let us know if you have any feedback or issues when using the devtools by creating a new discussion thread on Frog's GitHub repository.