# Source: https://nextjs.org/docs/pages/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/pages/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/pages/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/pages/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/pages/api-reference/config/next-config-js/devIndicators.md

# Source: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators.md

# devIndicators
@doc-version: 16.0.4


`devIndicators` allows you to configure the on-screen indicator that gives context about the current route you're viewing during development.

```ts filename="Types"
  devIndicators: false | {
    position?: 'bottom-right'
    | 'bottom-left'
    | 'top-right'
    | 'top-left', // defaults to 'bottom-left',
  },
```

Setting `devIndicators` to `false` will hide the indicator, however Next.js will continue to surface any build or runtime errors that were encountered.

## Troubleshooting

### Indicator not marking a route as static

If you expect a route to be static and the indicator has marked it as dynamic, it's likely the route has opted out of static rendering.

You can confirm if a route is [static](/docs/app/guides/caching.md#static-rendering) or [dynamic](/docs/app/guides/caching.md#dynamic-rendering) by building your application using `next build --debug`, and checking the output in your terminal. Static (or prerendered) routes will display a `○` symbol, whereas dynamic routes will display a `ƒ` symbol. For example:

```bash filename="Build Output"
Route (app)
┌ ○ /_not-found
└ ƒ /products/[id]

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand
```

There are two reasons a route might opt out of static rendering:

* The presence of [Dynamic APIs](/docs/app/guides/caching.md#dynamic-rendering) which rely on runtime information.
* An [uncached data request](/docs/app/getting-started/fetching-data.md), like a call to an ORM or database driver.

Check your route for any of these conditions, and if you are not able to statically render the route, then consider using [`loading.js`](/docs/app/api-reference/file-conventions/loading.md) or [`<Suspense />`](https://react.dev/reference/react/Suspense) to leverage [streaming](/docs/app/getting-started/linking-and-navigating.md#streaming).

## Version History

| Version   | Changes                                                                                                                                             |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `v16.0.0` | `appIsrStatus`, `buildActivity`, and `buildActivityPosition` options have been removed.                                                             |
| `v15.2.0` | Improved on-screen indicator with new `position` option. `appIsrStatus`, `buildActivity`, and `buildActivityPosition` options have been deprecated. |
| `v15.0.0` | Static on-screen indicator added with `appIsrStatus` option.                                                                                        |