# How long does a transfer take?

It depends which network you are sending to and from. As a general rule of thumb, L1 to L2 transfers take the same amount of time than sending via the native bridge. For example, depositing from Ethereum to Polygon takes approximately 22 minutes via the Polygon bridge and the same amount of time with the Hop bridge. This is because Hop **itself** uses the native bridges for L1 -> L2 deposits.\
\
The advantages with Hop come about when you transfer **the other way around** from L2 to L1 or from one L2 to another L2.\
\
Here, the rule of thumb is that an exit will take as many blocks to be considered final (safe from [reorgs](https://www.paradigm.xyz/2021/07/ethereum-reorgs-after-the-merge/)) on the sending chain. Some chains determine finality based on L1 consensus. The time-to-finality for these chains is not constant, so the values below will be an average based on the `safe` status of a block that a transaction is included in.\
\
\&#xNAN;*FYI: Hop has a* [*multichain block explorer*](https://explorer.hop.exchange/) *which allows you to track the status of your transaction as well as all your past transactions.*

### L2 to Any

* Optimism: \~25 minutes (finality)
* Arbitrum: \~12 minutes (finality)
* Nova: \~12 minutes (finality)
* Polygon: \~60 minutes (1600 blocks) (due to ongonig chain reorg issues)
* Gnosis: \~4 minutes (L2 finality)
* Base: \~25 minutes (finality)

### Ethereum to Any

* Optimism: \~2 minutes (optimistic finality)
* Arbitrum: \~10 minutes (finality)
* Nova: \~10 minutes (finality)
* Polygon: \~20 min (finality)
* Gnosis: \~30 min (light client finality)
* Base: \~2 minutes (optimistic finality)


---

# Agent Instructions: 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:

```
GET https://docs.hop.exchange/basics/how-long-does-a-transfer-take.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.