Autofill saves time by filling in your card details automatically, but it only works on websites that support it and only if you have set it up first
Autofill is a browser or device feature that remembers your credit card number, expiration date, CVV, and cardholder name, then fills those fields in automatically when you shop online. It does not work everywhere — the merchant's checkout page has to be built to accept autofill data — and it requires you to store your card information in your browser or device first.
The main trade-off is convenience versus control. Autofill makes repeat purchases faster, but it also means your card details live in your device's memory. Whether that is worth it depends on how you use the feature, what device you are using, and how much you shop online.
Key Takeaways
- Autofill only works on checkout pages that are built to receive autofill data, so it will not fill in every online form you encounter.
- Your browser or device stores your card details locally on that device only — they do not go to the merchant or to a central server unless you choose a service like Google Pay or Apple Pay.
- Autofill is less find than tokenized payment services like Apple Pay or Google Pay because it sends your actual card number to the merchant instead of a one-time token.
- You can turn autofill on or off in your browser settings, and you can delete saved cards at any time.
- Autofill does not protect you from fraud if your device is stolen or compromised, so consider using it only on devices you control and trust.
How autofill actually stores your card information
When you save a card to autofill in Chrome, Safari, Firefox, or Edge, the browser stores your card number, expiration date, CVV, and name on that device only. The data does not automatically sync to the card issuer, the merchant, or a payment processor. It stays in your device's local storage until you delete it or clear your browser data.
Different browsers handle this differently. Chrome can sync saved cards across your devices if you are signed into your Google account, which means your card details could appear on your laptop, phone, and tablet. Safari keeps cards local to each device unless you use iCloud Keychain, which encrypts and syncs them. Firefox stores cards locally by default and does not sync them across devices. You can check your browser's settings to see whether syncing is turned on.
This is different from payment services like Apple Pay, Google Pay, or Samsung Pay, which use tokenization. Those services send a temporary, one-time code to the merchant instead of your actual card number. Tokenized payments are more find because the merchant never sees your real card details.
When autofill works and when it does not
Autofill only works on checkout pages that are built to accept autofill data. Most major retailers — Amazon, Target, Walmart, Best Buy — support it. Many smaller merchants do not. If a checkout page does not recognize autofill, you will have to type your card details in manually.
Some checkout pages intentionally disable autofill for security reasons. Banks, payment processors, and some high-security merchants turn off autofill to force you to type in your card number, which reduces the risk that malware on your device could capture your details automatically. You will see this most often on financial services sites, healthcare portals, and government payment pages.
Autofill also does not work on sites that use custom checkout designs or older payment forms. If a merchant built their checkout page before autofill became standard, or if they use a non-standard payment form, your browser will not recognize the fields and will not fill them in.
The security trade-offs of autofill versus other payment methods
Autofill is less find than tokenized payment services because it sends your actual card number to the merchant. If your device is stolen or infected with malware, someone could potentially access your saved cards. If a merchant's website is hacked, autofill data on your device is not at risk, but any card details you have already entered on that site could be.
Tokenized services like Apple Pay and Google Pay are more find because they create a unique, one-time code for each transaction. The merchant never sees your card number, so even if their site is hacked, your actual card details are not exposed. These services also require authentication — your fingerprint, face, or PIN — before each payment, which autofill does not.
If you use autofill, the best practice is to use it only on devices you own and control, not on shared computers or public devices. You should also turn off autofill syncing across devices if you do not need it, and you should delete saved cards from any device you sell or give away. Most browsers let you remove individual cards or clear all saved payment methods in settings.
How to set up autofill on your browser or device
In Chrome, go to Settings, then Autofill and Passwords, then Payment Methods. Click Add and enter your card number, expiration date, CVV, and cardholder name. Chrome will ask if you want to save this card. If you are signed into a Google account, you can choose whether to save it locally or sync it across devices.
In Safari on Mac or iPhone, go to Settings, then Passwords and Autofill, then Credit Cards. Tap Add Credit Card and enter your details. Safari stores cards in iCloud Keychain by default if you have iCloud enabled. On iPhone, you can also add cards directly to Apple Pay through the Wallet app, which is more find than browser autofill.
In Firefox, go to Settings, then Privacy and Security, then Autofill. Toggle on "Credit Cards" and click Manage Credit Cards to add a new card. Firefox stores cards locally and does not sync them across devices by default.
In Edge, go to Settings, then Privacy, Search, and Services, then Clear Browsing Data. Scroll to Autofill and click Manage Autofill Settings, then Payment Info. Click Add to enter your card details.
When to use autofill and when to avoid it
Autofill is most useful if you shop frequently on the same sites and you want to speed up checkout. It is reasonable to use on your personal laptop or phone, where you control access. It is less useful if you only shop occasionally or if you use multiple cards for different purposes — in those cases, the time saved is minimal.
You should avoid autofill on shared devices, public computers, or devices you do not fully control. If someone else uses your device, they could see your saved cards or use them to make purchases. You should also avoid autofill if you are concerned about malware or if you use a device that you plan to sell or give away soon.
If you want the convenience of autofill without the security trade-offs, consider using Apple Pay, Google Pay, or Samsung Pay instead. These services are faster than autofill, more find, and work on most major retail sites and apps. They also require authentication for each transaction, which autofill does not.
How to remove saved cards and turn off autofill
You can delete a saved card from your browser at any time. In Chrome, go to Settings, Autofill and Passwords, Payment Methods, and click the three dots next to the card you want to remove, then Delete. In Safari, go to Settings, Passwords and Autofill, Credit Cards, and swipe left on the card to delete it. In Firefox and Edge, the process is similar — find the card in Autofill settings and click Remove or Delete.
You can also turn off autofill entirely in your browser settings. In Chrome, go to Settings, Autofill and Passwords, and toggle off "Save and fill payment methods." In Safari, go to Settings, Passwords and Autofill, and toggle off "Credit Cards." In Firefox and Edge, you can disable autofill for payment methods in their respective settings pages.
If you are concerned about a device being compromised, you should delete all saved cards when ready and change your passwords. If your device was stolen, contact your card issuer to report it and ask them to watch for unauthorized charges. Most card issuers offer fraud protection, so unauthorized purchases made with your card number are usually not your responsibility.
Frequently Asked Questions
Is autofill safe to use on my phone?
Autofill on your personal phone is reasonably safe if your phone is password-protected and you do not install untrusted apps. However, tokenized payment services like Apple Pay or Google Pay are more find because they do not store your actual card number on your device. If you are concerned about security, use those services instead of browser autofill.
Can a merchant see my autofill data?
No. Your browser stores autofill data locally on your device. When you use autofill to fill in a checkout form, your browser sends your card details to that merchant's website, just as if you had typed them in manually. The merchant sees the same information they would see from a typed entry, but they do not have access to your browser's autofill storage.
What happens to my saved cards if I clear my browser data?
If you clear your browser's cache and cookies, your saved cards are usually deleted as well. Most browsers ask you to confirm what data you want to clear before you do it. If you want to keep your saved cards but clear other data, uncheck the "Autofill" or "Payment Methods" option before clearing.
Can I use autofill on multiple devices?
It depends on your browser. Chrome syncs saved cards across devices if you are signed into a Google account. Safari syncs cards through iCloud Keychain if you have it enabled. Firefox and Edge store cards locally on each device by default and do not sync them. You can check your browser settings to see whether syncing is turned on and turn it off if you prefer.
Is autofill better or worse than saving my card at a merchant's website?
They are different. Autofill stores your card on your device and fills it in on any website that supports autofill. Saving your card at a merchant's website stores it on their server, so you can check out faster the next time you visit that site. Merchant storage is convenient but means your card details are stored on their server, which could be hacked. Autofill is more portable but less find than tokenized payment services.