> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/coti-privacy-portal/user-guide/convert-to-public-tokens.md).
# Convert to Public Tokens
The Private Tokens dashboard offers **Portal Out**, which converts private tokens back into standard public tokens. The portal uses the same pattern as Portal In: when the bridge needs permission to move your **private** balance, you **Approve** first, then confirm the withdrawal.
{% stepper %}
{% step %}
**Unlock and choose the asset**
* Ensure your private balances are unlocked (see [Setup Portal Account — Unlock private tokens](/coti-documentation/coti-privacy-portal/user-guide/setup-portal-account.md)).
* Select the asset from your **Private Tokens** list and enter the amount you want to withdraw.
Portal Out
{% endstep %}
{% step %}
**Approve (when the portal asks)**
* If the modal shows an **Approve** step, confirm it in MetaMask. This grants the privacy bridge permission to spend the **private** token amount you are withdrawing (encrypted allowance), similar to approving a public ERC-20 before Portal In.
* Wait until the approval transaction is confirmed. The UI will then let you continue to the actual withdrawal.
{% hint style="info" %}
Native **p.COTI** withdrawals also use an approval step for the native privacy bridge when required by the app flow.
{% endhint %}
{% endstep %}
{% step %}
**Confirm Portal Out (withdraw)**
* Click **Portal Out** (or the button shown to complete the withdrawal) and confirm the transaction in MetaMask.
* The private tokens are burned on the private side and the corresponding **public** tokens return to your wallet.
Confirm withdrawal in the wallet
{% 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://docs.coti.io/coti-documentation/coti-privacy-portal/user-guide/convert-to-public-tokens.md?ask=&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.
