Chrome beta v145 enables importing Safari data to Chrome iOS on iPhone

In this article

1. Overview: what's changing and why now
2. Technical Details: how export works on iOS and import in Chrome
3. Privacy Questions: what to assess before moving passwords and cards
4. What changes for the user: less friction when switching browsers on iPhone
5. Next Steps: when it arrives and how to prepare a clean migration
6. FAQ

Importing Safari data to Chrome iOS is now being tested in Chrome beta — and it changes how you switch browsers on iPhone Importing Safari data to Chrome iOS is the new feature Google has started testing in Chrome beta for iPhone, allowing you to bring your browsing information from Safari with fewer steps and no workarounds. The update, spotted in beta versions (v145), promises to make life easier for those who want to use Chrome as their main browser on iOS without losing browsing history, bookmarks and other data. For users who switch between ecosystems (Apple and Google) or use Chrome on desktop, this can reduce friction in the migration and make the experience more consistent.

Overview: what's changing and why now

Until now, switching from Safari to Chrome on iPhone was often an incomplete process: some data remained "trapped" in Safari, or required indirect solutions (partial syncing, unclear manual exports, or credential reconfiguration). With the option to import Safari data to Chrome iOS, Chrome now recognises an export file created by Safari itself and guides the user through the import inside the app. The important detail is the context: the feature appears first in beta. That is, it's not guaranteed that the final behaviour will be identical when it reaches the stable version, nor that all data types will have the same import reliability in all scenarios. For editorial transparency, the information was advanced by a Macworld article, which describes the export and import flow and the beta version where the option appears: Macworld's original article.

Technical Details: how export works on iOS and import in Chrome

The mechanism described is based on a simple principle: first iOS/Safari generates an export file; then Chrome reads that file and maps items to its internal areas (for example, bookmarks to bookmarks). In the reported scenario, the user exports data on iOS through the system Settings, in the Safari area, and saves the file in the Files app (Downloads). Next, in Chrome, they go to Settings and choose the option to import from Safari. In practical terms, this brings iOS closer to a more common desktop experience: "export from A" and "import to B", with an intermediary file. It's an approach that tends to be more transparent than "magical" syncing, because the user understands what they're transferring and when. What can be imported, according to the test description, includes categories like bookmarks and history, as well as sensitive items like passwords and cards. Here a note is worth making: when we talk about "extensions" on iOS, the concept is not equivalent to extensions in Chrome desktop; on iPhone, Safari extensions are a specific model of the Apple ecosystem, and real compatibility may vary. So, even if the list includes "extensions", it's plausible that the import is limited (or that it only brings metadata) — it's worth validating case by case. If you need official guidance on managing data in Safari and on iPhone, Apple's support base is the safest starting point: Apple Support. For options on syncing and data management in Chrome, Google's documentation helps you understand what stays associated with your Google account and what's local: Google Support.

Privacy Questions: what to assess before moving passwords and cards

Importing Safari data to Chrome iOS can include highly sensitive information. Even if the process is guided and seems simple, there are practical decisions to make before moving forward, especially if the iPhone is shared, managed by an organisation, or if there's a history of Google accounts used by multiple people. Points to consider: 1) Where the data ends up after import. Depending on Chrome settings, some of the content may start syncing with your Google account (useful for continuity between devices), but this also changes the "perimeter" of exposure: it's no longer just in the Apple ecosystem. 2) Duplication and inconsistencies. When importing history and bookmarks, you may end up with duplicate entries if you already use Chrome on other devices. A clean-up afterwards may be necessary to maintain organisation. 3) Passwords and cards are not the same as bookmarks. Bookmarks and history are relatively easy to review and delete. Credentials and payment methods require immediate verification after migration: confirm that imported entries are correct, that there are no outdated items, and that syncing is configured as you intend. 4) Export file. Since the process goes through a file saved in "Downloads", think about that file's lifecycle: after importing, it makes sense to delete it to reduce the risk of unintended access (for example, via file sharing or backups).

What changes for the user: less friction when switching browsers on iPhone

In practice, the big advantage of importing Safari data to Chrome iOS is reducing the cost of switching. Those who want to test Chrome as their main browser on iPhone tend to want three things: to keep bookmarks, not lose recent history, and continue signing into sites without reconfiguring everything. If the import delivers on what it promises, the transition becomes closer to a "fresh start with continuity" than a fresh restart. There's also a relevant secondary effect: by making migration easier, Google makes it more likely that users who already use Chrome on Windows, macOS or Android will align their iPhone with the same browser, reducing fragmentation of habits and data across platforms. On the other hand, it's important to keep expectations realistic while the feature is in beta. Availability may vary by region, by account, by iOS version and by Chrome's release schedule on the App Store. The original article mentions that the stable version didn't yet have this option at the time described, which suggests a wait before it reaches everyone.

Next Steps: when it arrives and how to prepare a clean migration

If your priority is stability, the recommendation is simple: wait for Chrome for iOS to reach the stable version. Betas may have interface changes, import failures or inconsistent behaviour. If you still want to experiment, do so with a rollback plan: ensure that you have access to your main credentials and that you can go back to Safari without losing access to essential services. To prepare a "cleaner" migration when importing Safari data to Chrome iOS: • Review before exporting. Delete old bookmarks and history you don't want to transfer. • Confirm the correct Google account. If Chrome syncs, make sure you're signed in to the right account before importing. • Verify after importing. Open a few critical sites (bank, health, work) and confirm logins and autofills. • Delete the exported file. After you've completed the process, remove the export file from the Downloads folder, if you don't need it. The end result, if the implementation holds, is a more "portable" iPhone between browsers: less reliance on a single ecosystem and more control over how data passes between apps.

FAQ

Is this feature available to everyone already?

Not necessarily. What was described appears in Chrome beta for iOS (v145). Arrival to the stable version depends on the end of the beta cycle and release on the App Store.

What do I need to import Safari data to Chrome iOS?

In terms of flow, you need to export the data in Safari through iOS Settings and save a file (for example, in Downloads), so you can then select/import it in Chrome in the app's Settings.

Can I choose only some data (for example, just bookmarks)?

According to the test description, the export screen allows you to select categories. The exact granularity may vary depending on the iOS and Chrome version.

Is importing passwords and cards safe?

It can be, but it requires care. You're moving sensitive data to another ecosystem and possibly to sync with a Google account. Check sync settings, confirm the correct account and delete the exported file after import.

What happens to the Safari export file?

It stays saved in the Files app (for example, in Downloads). After you've completed the import, it makes sense to delete it if you don't need it, to reduce the risk of unintended access.

If I already use Chrome on other devices, will I end up with duplicates?

It's possible. If you already have bookmarks and history in Chrome (via syncing), the import may create duplicate entries. Plan a review and clean-up after migration.

Get more articles like this one.

Refurbished tech analysis + €5 with BEMVINDO5 on your first order.

Subscribe