> For the complete documentation index, see [llms.txt](https://userguide.wlanpi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.wlanpi.com/hardware/wlan-pi-m4/powering-options.md).

# Powering options

## Power over Ethernet (PoE)

The M4 has built-in PoE circuitry. No additional power supply is required. This is the recommended option.

## USB-C port of your laptop

WLAN Pi M4 can also be powered by USB-C port of your laptop using USB-C to USB-C cable.

Some older laptops might not be able to provide enough power via USB. Please double-check.

<figure><img src="https://2540947589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY3fri1fsWlS5euhAG0JN%2Fuploads%2Fot4lJOoPWH94YzP3zLEA%2Fimage.png?alt=media&amp;token=e1f3b5f8-311a-4eea-969b-a8bdc78871c4" alt=""><figcaption><p>USB-C to USB-C cable</p></figcaption></figure>

## Apple USB-C PD MacBook chargers

While some MacBook USC-C chargers will charge the M4, some won't.

<figure><img src="https://2540947589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY3fri1fsWlS5euhAG0JN%2Fuploads%2Fy5603eB4c1CLEi63mtZk%2Fmacbook-charger.jpg?alt=media&amp;token=91755d84-53c8-41f8-be19-7fac182b456e" alt=""><figcaption><p>Supported USB-C Apple MacBook 60W charger</p></figcaption></figure>

<figure><img src="https://2540947589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY3fri1fsWlS5euhAG0JN%2Fuploads%2FGuoNb8no7OlroogkrfTp%2Fimage.png?alt=media&amp;token=b818cc1a-f13e-46cd-9309-939a1c33ce55" alt=""><figcaption><p>This USB-C Apple won't work</p></figcaption></figure>

## Power Distribution (PD) charger

A standard 5V USB-C PD charger is the best option.

### <mark style="color:red;">Warning</mark>

<mark style="color:red;">Please do NOT use non-PD power supplies with USB-C connector, that are not rated at 5V. Doing so will result in a magic smoke escape. We've tested that, so that you don't have to.</mark>

<figure><img src="https://2540947589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FY3fri1fsWlS5euhAG0JN%2Fuploads%2FY1qWLp9gTnTecHqhWRTz%2FIMG_1502.jpeg?alt=media&amp;token=512cd7e5-8a54-46d5-97f6-709a767e5a27" alt=""><figcaption><p>Incompatible 12V non-USB-PD power supply that fried our M4 unit</p></figcaption></figure>


---

# 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://userguide.wlanpi.com/hardware/wlan-pi-m4/powering-options.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.