Feature Request: Thumbnail preview domain block list

I noted some other old threads on this issue ...

Can you please add a black-list for common tracking and advertising domains so that 1Password does not make requests to these domains when examining the webpages associated with a login.

Its depressing to see littlesnitch report 1password looking at these domains. It has to be smarter than that.


  • khadkhad Social Choreographer

    Team Member

    It sounds like you are referring to 1Password fetching previews of the sites for which you have saved Login items.

    When you create a new Login 1Password will contact the web site to generate a page preview which is displayed in the detail view of the Login. It will also try to fetch apple-touch-icon.png and favicon.ico from the web server. This are used for displays in shelf and list views of your data. 1Password does not send any information to the sites it fetches these from other that the actual URL you have stored for the site.

    If 1Password cannot do the fetching immediately when the Login is created, then it will periodically try to get these at a later time. This can happen, for example, when a Login is created in 1Password for iOS, which doesn’t fetch icons, and then synchronized with 1Password for Mac or Windows, which do fetch icons and previews. In these cases on the Mac the connection will be initiated by 1PasswordThumbs.app within the 1Password.app application bundle.

    You may control automatic preview fetching in the Logins preferences pane by checking or unchecking “Automatically download icons and previews for new Logins” in the Logins preference pane.

    Finer grained control such as adblocking or domain blocking is something we can consider for the future, but I believe the issue will be irrelevant when 1Password 4 for Mac debuts since it does not create previews in the same manner but rather uses the image server like 1Password 4 for iOS.

    If we can be of further assistance, though, please let us know. We are always here to help!

This discussion has been closed.