> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/polygon-bridge-types-for-beginners.md). # Polygon Bridge Types for Beginners Polygon Bridge moves supported tokens between Ethereum and Polygon PoS, provided your token has a route between the two networks. For beginners, the main options are the PoS bridge, the Plasma route used by native POL, and liquidity bridges. The right route depends first on the token you hold, then on the time and cost shown for the transfer. ### Which Polygon Bridge Type Fits Your Token? The three main routes differ in how they deliver tokens and which assets they can carry. Start by checking the token and destination network; a faster quoted route is no help if it delivers a different version of the asset than you need. For a bridge from Ethereum to Polygon, check that the token is supported and that your wallet can access both networks. When you are ready to move it, use the [Polygon Bridge](https://polygonbridge.dev) to send supported tokens to Polygon or return them to Ethereum. The route used for that transfer determines how its completion is recorded. * **PoS bridge:** Best for a token mapped between Ethereum and Polygon PoS through the native bridge contracts. It does not fit an unmapped token or native POL, which has a different withdrawal path. * **Plasma route:** Best when an asset’s established path calls for it, notably native POL leaving Polygon. It is not a general replacement for the PoS route; check its current exit requirements before starting. * **Liquidity bridge:** Best when a provider can quote a transfer using funds available on the destination chain. It does not fit when liquidity is insufficient or the quoted fee and price impact make the received amount unacceptable. polygonbridge.dev is a service for moving tokens between Ethereum and Polygon. Whichever route you use, check the asset’s contract address on the receiving network: tokens with similar names can represent different assets. ### What Happens to My Tokens When I Bridge Them? On the native PoS bridge, an Ethereum deposit locks the original tokens in a Predicate contract, and a corresponding balance becomes available on Polygon. Polygon Support describes this as a one-to-one lock and mint process. For a mapped ERC-20 token, an illustrative deposit of 100 units produces 100 corresponding units on Polygon before transaction costs. Returning through that route reverses the process: the Polygon tokens are burned, then a proof of that burn lets Ethereum’s RootChainManager release the locked tokens. Polygon’s PoS Portal contracts specify that exit flow. A liquidity bridge works differently: it pays from available funds on the destination chain and settles with its own liquidity providers, so the amount you receive follows its quote. This distinction matters most when withdrawing. A Polygon transaction that burns tokens is not necessarily the last action: a native bridge withdrawal can still need an Ethereum claim after a checkpoint records the burn. Keep enough ETH for that claim even if the tokens no longer appear in your Polygon wallet. ### How Do I Bridge Tokens From Ethereum to Polygon? Connect a wallet such as MetaMask, choose Ethereum as the source and Polygon PoS as the destination, then verify the token and amount before signing. The basic sequence is: 1. Check that you hold the supported token on Ethereum and have ETH there for gas. 2. Choose the route available for that token and inspect the expected amount on Polygon. 3. If the token requires an ERC-20 approval, confirm that transaction before confirming the deposit. 4. Confirm the bridge transaction, wait for it to complete, and view the balance on Polygon PoS. Polygon bridge fees depend on Ethereum gas, any approval transaction, and the route’s own charges; a liquidity route may also include price impact. You will need POL for later transactions on Polygon. Before signing, check the destination network, token contract, received amount, and any remaining claim step in one pass. If you bridged this token back tomorrow, which route would return the asset you actually want, and what would you need to pay to finish the withdrawal? --- # 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://aboutcryptotalks.gitbook.io/aboutcrypto/polygon-bridge-types-for-beginners.md?ask=&goal= ``` `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.