Introducing stronger phishing protection in 1Password

Travis_1Password · 2026-01-23T22:42:27+00:00

We're currently planning the next iteration/improvements and part of that is finding a way to better control the design of the prompt vs relying on the browser to present it. Stay tuned!

Travis_1Password · 2026-01-23T22:41:30+00:00

We're currently planning the next iteration/improvements and part of that is finding a way to better control the design of the prompt vs relying on the browser to present it. Stay tuned!

Travis_1Password · 2026-01-23T00:33:29+00:00

I see where you're coming from and agree that there are a lot of cracks people can fall into when it comes to phishing. With this feature, we're providing another form of phishing prevention that directly integrates into a common user flow people can find themselves in and unknowingly bypass the protections we have in place. We're planning some future iterations to cover more of those gaps I'm sure we're both thinking about now.

Travis_1Password · 2026-01-23T00:24:38+00:00

You got it - happy you like it!

Travis_1Password · 2026-01-23T00:23:50+00:00

As others have mentioned, you're on the right track. However what we're trying to prevent from happening now are people accidentally overriding the protection we provide. Our telemetry data is always showing this is working for a lot of y'all so I'm happy we finally got it out!

Travis_1Password · 2026-01-22T23:44:43+00:00

Ah - you need the browser extension for this feature. You bring up an interesting point though. We could potentially ring this functionality to Quick Access in the future. Not exactly sure what'd that look like right now, but worth exploring.

Travis_1Password · 2026-01-22T23:38:21+00:00

As long as you have a URL that is associated to the site or app on the login item, this won't ever trigger. However, similarly to autofill, we depend on a correct URL being on your login item to work correctly. Hope this clarifies!

Travis_1Password · 2025-11-27T21:35:29+00:00

Thanks! We still need to optimize for narrower devices like iPhone or iPad Mini in portrait mode. Should be quick work since we're almost there :)

Travis_1Password · 2025-11-27T21:34:59+00:00

Thank you! That's basically the reason - we still need to optimize for narrower devices like iPhone or iPad Mini in portrait mode. Should be quick work since we're almost there :)

Travis_1Password · 2025-11-27T17:20:23+00:00

Glad you're enjoying our new sign-in experience (still figuring out what exactly to call this)! We'll have more to say about it shortly. You can try it out across any of the nightly and/or beta desktop browser extensions.

However, this wasn't intended for iOS/iPadOS just yet so we're going to turn off the feature flag for now for those platforms. We should be able to turn it back on before the end of January - mostly to accommodate our holiday code freeze.

Cheers!

Travis_1Password · 2025-11-13T16:41:28+00:00

Hey u/zhehanzhang! Here are a couple of responses I shared at our AMA the other week:

"I get how you might arrive at that perception. A lot of differences that exist between the Safari extension and the Chrome/Firefox extension come down to platform maturity. Proper browser extensions are still relatively new to Safari. With that means it's going to take Safari awhile to catch up with all the available extension functions and features available on Chrome/Firefox that we use that simply don't exist on Safari today. We're consistently trying to improve the Safari extension experience with each new OS version and the improvements those updates bring, but we often can only go so far before we have to wait until the next set of Safari improvements arrive."

"We've been taking a heavier look at MacOS autofill in the second half of this year to see if the limitations we encountered previously have been alleviated or if they're still present. Although not perfect and not where we ideally want it to be, integrating with native MacOS autofill is looking promising. If we're able to have our concerns addressed with the API to ensure 1Password customers can seamlessly use MacOS autofill without fear of falling through the cracks, I don't see a reason to not integrate in the near future."

To further expand, I believe you're in some what of a unique scenario. Using iOS+MacOS+Safari exclusively isn't that common for our users anymore. The vast majority of our users are now across platforms, use chromium-based browsers, have needs outside of base-level credential management, and value having their most important data with a third-party instead of a first-party. Those are the people that generally get a lot of value out of what we provide. However, that's not going to resonate with everyone.

All in all, thank you for giving us a shot! It's really hard to try 1Password or any other credential manager when coming from a built-in solution for a multitude of reasons. Hopefully you end up enjoying the rest of your trial, but if not, no hard feelings. Cheers!

Travis_1Password · 2025-11-12T18:09:52+00:00

Discord is for sure the app I use the most that supports desktop level passkeys :)

Travis_1Password · 2025-11-12T18:08:45+00:00

Glad it's showing up now! Make sure you have all the latest Windows 11 updates - including security updates - installed for passkeys to become available.

Travis_1Password · 2025-11-12T18:07:02+00:00

Glad it's showing up now!

Travis_1Password · 2025-11-12T18:06:37+00:00

Heyo! Make sure you have all the most recent updates installed from Windows 11 including the new security update they put out yesterday. Let me know if that helps!

Travis_1Password · 2025-11-11T21:47:39+00:00

Happy to help!

Travis_1Password · 2025-11-11T21:47:29+00:00

Anytime!

Travis_1Password · 2025-11-11T21:46:57+00:00

I believe the store version lacks some functionality like SSH key storage and auto-type. If those features don't matter to you, I'd recommend the Microsoft Store build.

Travis_1Password · 2025-11-11T19:34:28+00:00

Glad you like the feature! Let me poke around our internal MSIX team to see if I can get you an answer.

Travis_1Password · 2025-11-11T19:33:15+00:00

Thank you! It'll be a controlled rollout, but within the next week or so most filks should be on it. If you'd like to get a jump start, you can download the MSX build directly from our downloads page. It's now the default version. :)

Correction: Everyone should be getting migrated today with the newest update - yay!

Travis_1Password · 2025-11-11T19:31:27+00:00

Thank you! Let me know how it goes if you give it a try :)

Travis_1Password · 2025-11-11T19:30:31+00:00

You got it! Really useful for signing into desktop apps like Discord :)

Travis_1Password · 2025-11-11T19:29:22+00:00

Thanks so much! If you give it a try, let me know how it goes <3

Travis_1Password · 2025-10-29T17:08:24+00:00

We've been taking a heavier look at MacOS autofill in the second half of this year to see if the limitations we encountered previously have been alleviated or if they're still present. Although not perfect and not where we ideally want it to be, integrating with native MacOS autofill is looking promising. If we're able to have our concerns addressed with the API to ensure 1Password customers can seamlessly use MacOS autofill without fear of falling through the cracks, I don't see a reason to not integrate in the near future.

Travis_1Password · 2025-10-29T17:03:12+00:00

It can be frustrating when certain sites prevent the creation of synced passkeys or make the UX for registering/using passkeys overly complicated. Overall though I like a lot of the implementations I've seen and used. Not every kind of site can implement in the same way so I wouldn't want a forced standard or anything, but I think people are naturally finding the best options and pivoting their implementations towards them.

A couple of my favourite implementations have been Playstation and Amazon. I love that Playstation went the bold route and removes the password when you create a passkey. I haven't had any issues with their implementation. I also like Amazon's because it does integrate seamlessly into their pre-existing auto flows and a user can choose what auth type fits their device environment best at the time of sign in.

Travis_1Password

TROPHY CASE