> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/configuration/view-and-edit-camera-settings/find-a-cameras-serial-number-and-mac-address.md).

# Find a Camera's Serial Number and MAC Address

Locate a camera’s serial number and MAC address

You need a camera’s serial number to add it to Command before it can be accessed and managed.

Knowing a camera’s Media Access Control (MAC) address can be useful in troubleshooting, static Dynamic Host Configuration Protocol (DHCP) assignments, firewall allowlists, and so on.

You can find a camera’s serial number and MAC address on the [camera label](#h_a39c069cd2) and the [camera’s settings page](#h_5539707d87) in Command.

{% hint style="warning" %}
All Verkada MAC addresses start with **E0:A7:00**.
{% endhint %}

***

### Camera label

On the bottom of each camera, you can find a label that contains the serial number, a quick-add QR code, and the MAC address.

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-22ebba50f59b056b63800aee511e6706978d9e38%2F1cd7438b9a36c5d1c54ee991e016c2f344dfd87c.png?alt=media" alt="" width="563"></div>

***

### Camera settings page

A camera’s MAC address will display in Command once it comes online.

{% hint style="danger" %}
You need [Org Admin permissions](/command/users-and-permissions/roles-and-permissions-for-command.md) to view a camera’s MAC address in Command.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**Select the camera.**
{% endstep %}

{% step %}
**In the bottom right, click Settings.**
{% endstep %}

{% step %}
**Under General, you can find the serial number, MAC address, and other settings.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-61826a270029b47bcb6489a96a94d114cc21d2dd%2F0071a9d026bc0bd454d294250b750adb597ba794.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/verkada-cameras/configuration/view-and-edit-camera-settings/find-a-cameras-serial-number-and-mac-address.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.