At a more generalized level then some of the other replies: password and secure information management is a specific set of tasks and requirements that are orth

At a more generalized level then some of the other replies: password and secure information management is a specific set of tasks and requirements that are orthogonal to web browsing. Abstracting that out into an independent piece of software makes it much easier to swap either side. It's much easier to jump from one web browser to any other web browser if there is no information transfer between them required. It's much easier to use multiple browsers simultaneously for the same reason. It's much easier to move from one password manager to another if that doesn't affect any other application that plugs into it at all. Decentralizing and fragmenting authentication and secure information is a problem. Additionally dedicated problem programs tend to be more responsive and featureful then when the functionality is tacked on non-core in something else. Password managers facilitate sharing within groups and organizations for example in a secure and structured way. For many people that may be one of their most valuable features in fact, right down to the level of families. I mean, this basic philosophy shows up a lot in computing right? For example, it's an important idea at least at the heart of some of the original Unix style of doing things, where you have lots of independent programs that do something well and then link them for more complex operations rather then everything-and-the-kitchen-sink. The latter has its place sometimes too but there are strengths to the former, or to programming styles that splits up larger systems into smaller tasks joined together.