> For the complete documentation index, see [llms.txt](https://meshnet.nordvpn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meshnet.nordvpn.com/features/renaming-devices/android.md).

# Renaming devices on Android

This page provides instructions for renaming devices in your Meshnet on the Android app.

## Rename a device

To rename any device in your Meshnet, follow these steps:

1. Open **NordVPN** and go to **Products** <img src="/files/fnGLtxGkWpaBrxQKqCU4" alt="" data-size="line"> > **Meshnet** <img src="/files/ZKtk7xbdpRRtNXmrvNrx" alt="" data-size="line">.
2. Depending on which device's name you want to change, do one of the following:
   * To rename this device, tap the three-dot menu next to your device and select **Rename**.

     <div align="left"><figure><picture><source srcset="/files/qWrxC8sdn81hFZq5h8yK" media="(prefers-color-scheme: dark)"><img src="/files/VUe5lh8pFGaCnXzunvs0" alt="&#x22;Rename&#x22; option highlighted from the three-dot menu next to &#x22;Your device&#x22;." width="375"></picture><figcaption></figcaption></figure></div>

     &#x20;
   * To rename a peer device, select **Manage devices**, then, next to the device you want to rename, tap the three-dot menu, and select **Rename**.

     <div align="left"><figure><picture><source srcset="/files/3ENMbG7iN3KJmvqeGjnt" media="(prefers-color-scheme: dark)"><img src="/files/TSikG3DX7dEkKtyO5iIE" alt="&#x22;Rename&#x22; option highlighted from the three-dot menu." width="375"></picture><figcaption></figcaption></figure></div>

     &#x20;
3. In the **Device name** field, replace the pre-filled Nord name with the new nickname you want the device to have.
4. Tap **Save** to apply the change.

   <div align="left"><figure><picture><source srcset="/files/EPsZgjdkCH1x4UG2VPY3" media="(prefers-color-scheme: dark)"><img src="/files/veJZhYkZypbFKY3B7VQP" alt="&#x22;Save&#x22; button highlighted on the &#x22;Rename device&#x22; sheet." width="375"></picture><figcaption></figcaption></figure></div>

The new custom nickname for the device should now be displayed in your Meshnet device list and synced across all your personal devices.

<div align="left"><figure><picture><source srcset="/files/Bc7JDE34F1F6qiJyAjJ7" media="(prefers-color-scheme: dark)"><img src="/files/h5Ay78Q6n6Sm4WvlzTzL" alt="Updated name of the device highlighted." width="375"></picture><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note**

To remove a device's nickname and restore it to the original Nord name, on the **Rename device** bottom sheet, tap the **Reset to Nord name** button, and then select **Save**.
{% endhint %}

## See also

* [Renaming devices on Windows](/features/renaming-devices/windows.md)
* [Renaming devices on iPhone/iPad](/features/renaming-devices/ios.md)
* [Renaming devices on macOS](/features/renaming-devices/macos.md)
* [Renaming devices on Linux](/features/renaming-devices/linux.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://meshnet.nordvpn.com/features/renaming-devices/android.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.