SQL Server Master Data Services database history by snapshots
Snapshots do have some performance overhead. With a dozen snapshots you could have up to 12 additional pages written to disk for each page written to the main DB, depending on your write patterns.

Consider what you want to do with these snapshots.  If they're simply for putative future auditing then do a backup and get them off your production server.  You can restore them when they're needed.  Ad hoc analysis?  best not done on the production server (and engaging the live DB) either.  Disaster recovery?  DB snapshots do not give you that.  To revert to in the event of a mistake?  You'll be rolling back a lot of other work, too, which would have to be re-done.  Then-versus-now analysis.  Hmmm, maybe.

In short, a "proper" backup, restored as an independent database and only db_reader granted will be better in almost every way.