An Ethereum user sees three gas price options in MetaMask: Low, Standard, and High. The wallet estimates that Low will cost 25 gwei per unit of computation, Standard will cost 35 gwei, and High will cost 50 gwei. The user clicks High, assumes the transaction will be fast, and waits. Three hours later, the transaction remains pending. The question then becomes not why it is slow, but why the “high” setting did not solve the problem. The answer reveals how MetaMask’s fee marketplace translates user choices into blockchain outcomes, and why network conditions can render even aggressive fee settings ineffective.
MetaMask does not set gas prices directly. It estimates what a miner or validator will accept based on recent blockchain activity, network congestion, and algorithm defaults. The fee marketplace is a continuous auction: as demand for block space increases, the cost to compete for that space increases. MetaMask’s three-tier interface simplifies that auction into recommendations. But simplification creates a gap between what users expect and what actually happens when they submit their transaction. Understanding that gap is essential for anyone who wants to control cost, speed, and reliability rather than merely hoping the selected tier will work.
How gas price estimation works in MetaMask
MetaMask’s gas recommendations come from multiple sources. The wallet can query an oracle such as Etherscan, use a provider’s own data, or calculate estimates from recent blocks. For Ethereum mainnet, the Standard tier typically targets inclusion in the next twelve blocks (around three minutes), while High targets faster inclusion. Low assumes the user is willing to wait or that network congestion will ease. These are estimates, not guarantees. The wallet makes its calculation at the moment you open the send dialog, which means the network state when you confirm the transaction may differ significantly.
The base fee, introduced in Ethereum’s London upgrade, is a key component that MetaMask displays. This is a minimum price per unit of gas that validators will accept; it burns automatically and does not go to the miner or validator. The priority fee (also called the tip) is what you add above the base fee to incentivize faster inclusion. MetaMask’s High setting typically increases the priority fee substantially, while Low reduces it. The wallet may also apply its own margin or adjustment factor, which can cause the same network state to produce slightly different estimates depending on the timing of your request.
Custom gas settings allow users to override MetaMask’s recommendations entirely. You can enter your own gas price (on non-Ethereum networks) or adjust the base fee, priority fee, and gas limit separately on EVM networks. This flexibility is powerful and dangerous. Too low a priority fee on a congested network can leave your transaction queued indefinitely. Too high a gas limit can cause your transaction to waste funds on unused computation. MetaMask displays a warning if your settings are far outside recent norms, but the warning does not prevent submission. The final decision and the final cost remain your responsibility.
When Low gas makes sense and when it does not
Low gas is economically rational when either time does not matter or when you believe network congestion will ease soon. A non-urgent token transfer, a scheduled operation, or a transaction submitted at 3 AM UTC when Ethereum traffic historically drops can afford a minimal priority fee. Some users batch transactions or submit them on nights and weekends specifically to exploit these low-congestion windows. For interactions with lending protocols, staking operations, or internal portfolio adjustments, waiting six to twelve hours may cost far less than paying for an aggressive fee during peak hours.
Low gas becomes risky during network events: large token launches, popular NFT drops, major market movements, or protocol updates. These events can sustain high base fees for hours. A transaction submitted with Low gas during a spike may never confirm until the spike ends, then appear to settle much later than intended. If you are capturing arbitrage, claiming time-sensitive rewards, or competing for scarce NFTs, Low gas is almost certain to fail. The saved gas fee becomes irrelevant if your transaction does not execute before the opportunity closes.
MetaMask’s Low tier also assumes you are not price-sensitive to the gas price itself, only the total cost of your transaction. If you are swapping tokens with a price impact calculation, a delayed transaction may settle at a worse rate than expected. The slippage protection built into many DEX interfaces can reject swaps that execute at worse prices; your Low-gas transaction might sit in the mempool for two hours, then fail when it finally mines because the expected output no longer matches the current market price. In these cases, paying for Standard or even High gas protects against total failure.
Standard gas and market conditions
Standard gas is MetaMask’s baseline recommendation and represents a balance between cost and reasonable expectation of inclusion. On quiet networks, Standard typically results in confirmation within five to fifteen minutes. During moderate congestion, confirmation may take thirty to sixty minutes. Standard is the right choice for most routine transactions: token transfers between your own wallets, withdrawals from exchanges, or interactions with DeFi protocols where execution happens within the same minute or minute range matters less than overall throughput.
The relationship between Standard and actual confirmation time is not linear. A Standard fee adequate at 10 AM on Tuesday may be far too low during a flash event at 11 AM on Wednesday. MetaMask recalculates estimates continuously, but the wallet cannot predict future events. If you submit a Standard transaction at moderate congestion, then the network experiences a sudden surge (a popular new token launch, a DeFi flash loan cascade, a malicious MEV event), your transaction may slip backward in the queue. New transactions submitted minutes later at higher fees will jump ahead. You will still pay the Standard fee rate, but your confirmation time will become much longer.
A practical strategy is to increase from Standard to High if your transaction fails to confirm within the expected timeframe, then use the Replace-By-Fee (RBF) feature to speed it up. MetaMask allows you to cancel pending transactions or bump their fee. Canceling submits a zero-value transaction with the same nonce to remove the original. Bumping creates a new transaction with the same nonce but a higher fee, allowing the network to accept the replacement. Both approaches consume additional gas for the second transaction, so the total cost exceeds what you would have paid with a single High-fee transaction. Yet if Standard would have succeeded without the bump, you save money overall.
High gas and the paradox of failed priority transactions
High gas should theoretically guarantee fast inclusion. MetaMask sets the priority fee well above recent median values, signaling to validators that you are willing to pay premium prices. In normal network conditions, this works reliably: confirmation within one to three minutes. During extreme congestion, High gas can still fail to deliver the expected speed or can be outbid by transactions submitted later with even higher fees.
This paradox arises because gas fees are dynamic. When Ethereum processes blocks at capacity, the base fee automatically increases. New transactions submitted seconds after yours may legitimately offer higher total fees because the base fee itself has risen. Your High-fee transaction remains in the mempool, not forgotten, but no longer the highest bidder. Validators will prioritize the newer, higher-fee transaction. You are stuck. Your transaction is correct, your fee is objectively high, and you will eventually confirm, but not as quickly as you expected.
A second failure mode occurs when the network is congested but not uniformly. Different validators, mining pools, and validators can implement slightly different transaction selection strategies. Some prioritize absolute fee rate; others include MEV (maximal extractable value) considerations, meaning they order transactions not by fee but by profitability to the validator. Your swap might offer less MEV profit than a sandwich attack or liquidation that a validator can extract by reordering transactions. Your High fee is irrelevant to that calculation.
The most frustrating case happens when the network is congested but becoming less congested. You submit a High-fee transaction at peak congestion. By the time a block has space for it, the base fee has already started falling. Validators will include lower-fee transactions that arrived later, because those newer transactions now offer higher priority fees relative to the new, lower base fee. Your transaction sits waiting. This is not a MetaMask failure; it is a consequence of how Ethereum’s EIP-1559 mechanism works when demand is volatile. Patience is sometimes the only solution.
Custom settings and the risk of miscalculation
MetaMask’s custom gas editor provides two modes: Basic (priority fee and base fee) and Advanced (full control of gas limit, base fee, and priority fee). Power users often edit these fields to save money on routine transactions or to respond to specific network conditions. The risk is that a mistake in either the gas limit or the priority fee can cause your transaction to fail, execute incorrectly, or cost far more than intended.
Gas limit errors are particularly common. If you copy a custom gas limit from a previous transaction but apply it to a different operation—perhaps a token swap instead of a simple transfer—you might set a limit that is too low. The transaction will fail midway through execution with an out-of-gas error. Your MetaMask wallet security remains intact, but your fee is wasted. MetaMask does warn you if your custom limit is below the default, but the warning can be easy to dismiss if you are in a hurry.
Priority fee mistakes can be costlier. Setting a priority fee of 1 gwei instead of 100 gwei during congestion means your transaction may not confirm for hours, if at all, before the network clears. Setting it to 1000 gwei when 50 gwei would suffice wastes significant money. Because blockchain transactions cannot be edited after submission (only replaced with higher fees), you bear the full cost of the mistake. MetaMask shows you the estimated total cost before you confirm, but mental math is error-prone and urgency encourages skipping that step.
A defensive practice is to make one small test transaction at your custom settings before committing significant funds. This costs a little in fees but prevents catastrophic errors. For the MetaMask mobile wallet download, the interface is more compact, making custom editing riskier. Desktop versions allow easier review of parameters before confirmation.
Network congestion patterns and predictable windows
Ethereum’s congestion is not random. Certain times consistently experience lower demand and lower base fees. Late night and early morning hours UTC typically see reduced activity because Asia is offline and American markets are closed. Weekends and especially Sundays have lower volume than weekdays. The first few blocks after major network events (token launches, protocol upgrades) often clear accumulated transactions, creating a brief window when fees drop.
Savvy users exploit these windows by submitting transactions during off-peak hours, then using Low or Standard gas fees with confidence. A token transfer submitted at 2 AM UTC on a Sunday morning likely confirms within minutes despite Low gas. The same transaction at 2 PM UTC on a Thursday during a market shock may take hours or fail. MetaMask cannot predict these patterns; the wallet reacts to current conditions. An experienced user layers MetaMask’s recommendations with external knowledge about when their network tends toward congestion.
MEV (maximal extractable value) also follows patterns. High-frequency trading activity concentrates around major market moves and during US trading hours. Sandwich attacks and liquidation cascades are more common during volatile periods. If you are executing a large swap, your transaction is more likely to be frontrun (a malicious reordering where a validator observes your pending swap, submits a transaction ahead of yours to move the price, then places yours after it) during these windows. A higher priority fee does not prevent frontrunning, but it may reduce the time your transaction sits in the mempool exposed to MEV detection.
Practical strategies for different transaction types
Routine transfers (sending tokens to your own wallet, moving assets between accounts, or withdrawing from known addresses) should use Standard gas unless you need immediate confirmation. Even if confirmation takes an hour, the delay is typically acceptable. Low gas works if you are transferring before sleeping or before a planned downtime. High gas is wasteful unless you have a specific deadline.
Swaps and DEX interactions require more care. If you are trading on a popular protocol during market hours, use High or edit your priority fee to ensure confirmation within one to two blocks. The price impact of a delayed transaction can exceed the cost of higher gas. If you are trading a volatile or illiquid token, slippage is especially high; paying for fast inclusion reduces the risk that your transaction confirms at a terrible rate. For large swaps that might create MEV opportunities, a high gas fee may also reduce sandwich attack incentives, though it does not eliminate them entirely.
NFT operations are even more time-sensitive. Competitive minting, secondary-market purchases, or claims with limited quantity require fast confirmation. Use High gas or edit to above-market priority fees. The cost of failing to mint or losing an auction is often much higher than paying extra in gas. Be aware that during major drops, network base fees can spike to 100+ gwei, making even High gas expensive. Some users intentionally submit transactions slightly after a drop starts, accepting that they might miss it, to avoid the worst congestion peak.
Staking, governance, and other protocol operations are usually not time-sensitive. Standard gas is typically appropriate. If you are claiming rewards or unstaking before a deadline, allow extra time and use Standard or High gas depending on how close you are to the deadline. If the operation is part of a time-sensitive strategy (e.g., liquidation or arbitrage), prioritize speed and pay for High gas.
When your High-fee transaction still does not confirm
If a High-gas transaction remains pending for more than five minutes on Ethereum mainnet during normal to moderate congestion, the network is experiencing unusual demand or your transaction has encountered a specific problem. First, verify that the transaction was actually submitted. MetaMask’s “Activity” or transaction history should show it. If it is not there, the transaction was rejected before broadcast, often due to insufficient funds, nonce conflicts, or a gas limit that is too low for the operation.
If the transaction appears in your MetaMask history as pending, check a block explorer such as Etherscan. Search for your wallet address and look for the specific transaction. The explorer will show its status (pending, success, or failed), the fee you actually paid, and how many confirmations it has received. If Etherscan shows the transaction as pending and your gas fee was genuinely high, the likely explanation is a nonce problem. Each transaction requires a nonce that increments. If you submitted two transactions quickly and the second one is stuck, the first one might have failed or been delayed, causing the second one to wait behind it.
To unstick a stuck transaction, you can cancel it by submitting a zero-value transaction with the same nonce but a higher fee, or replace it with a transaction that has the same nonce but a higher fee. MetaMask’s Speed Up and Cancel buttons automate this for pending transactions. Clicking Speed Up increases the gas price and resubmits; clicking Cancel submits a zero-value transaction to that same nonce. Both cost additional gas. If you choose Cancel, you will pay gas for both the cancellation and any subsequent transaction you submit.
In extreme cases, if the network remains congested for hours and your transaction is very old, you might choose to increase the gas even further or wait for the network to calm down. Patience sometimes costs less than continuous fee bumps. MetaMask will not automatically manage this; you must make the decision and execute the action yourself.
Fee marketplace evolution and staying informed
MetaMask’s fee recommendations are only as good as the data sources they use. The wallet can query Etherscan, EIP-1559-Explorer, or a provider’s own estimation engine. Different sources sometimes give different recommendations because they use different algorithms and time windows. During market transitions (especially during large MEV events or network upgrades), estimates can become stale within seconds.
Users interested in understanding their options beyond MetaMask’s three tiers can consult external gas tracking tools such as Etherscan’s Gas Tracker or Ultrasound.money. These show real-time base fee, recent transaction prices, and historical trends. Understanding this data helps you make more informed custom settings or decide whether to wait for congestion to ease.
MetaMask also continues to evolve its fee infrastructure. The wallet now supports better UX for RBF (Replace-By-Fee) and cancel operations. On scaling layers like Arbitrum, Optimism, and Polygon, gas prices are much lower, making fee management less critical. On Layer 2 networks, Standard gas may cost cents instead of dollars, so the High versus Low choice matters far less. As Ethereum’s own scaling roadmap continues (via proto-danksharding and other upgrades), base fees may fall, but the auction mechanism will remain the fundamental driver of user cost and confirmation speed.
Frequently asked questions
Why did my High gas transaction confirm slowly or not at all?
High gas increases your priority fee, but during peak congestion, newer transactions submitted seconds later may have even higher total fees due to rising base fees. Validators prioritize the highest bidders, so your transaction can still be delayed. Additionally, if the network’s demand drops after you submit, lower-fee transactions arrive and confirm first. Extreme congestion, nonce conflicts, or MEV considerations can also prevent fast inclusion. Use a block explorer to check your transaction status.
What is the difference between gas price and priority fee in MetaMask?
On Ethereum and EVM networks using EIP-1559, the total fee has two parts: the base fee (which burns) and the priority fee (which goes to validators). MetaMask’s Advanced settings let you edit both separately. The priority fee is what you compete with other transactions on; a higher priority fee helps you jump ahead during congestion. The base fee is automatic and increases with network demand; you cannot control it, only observe it.
Should I always use High gas to guarantee fast confirmation?
No. High gas improves your chances during normal or moderate congestion but does not guarantee speed during extreme demand. For non-urgent transactions like routine transfers, Standard or even Low gas is appropriate and saves money. Use High gas for time-sensitive operations like swaps during market volatility, competitive NFT mints, or protocol operations with deadlines. During off-peak hours (nights and weekends UTC), even Low gas typically confirms quickly.