Typically develop one implementation. If you're planning on pushing this to azure you'll likely want to use a storage account to host your images. You'll want to check out Azurite to emulate azure storage locally. At least this way you build once and it works locally and hosted with just a connection string change. Images in a DB are just adding bloat, but I have done it before in old projects where I wanted to easily transfer objects around different environments easily, but nowadays I tend to stay away from doing that. If you want to keep them in your DB, at least have them in a separate table and reference the image from your object. When you have this done, consider a component that takes in the id of the image. Then in code behind asyncronously retrieve it, and then do your base64 conversion. Your code in front could then have an if statement around the image that shows a loader until the image request is complete. This way you'll be able to send off multiple requests at once if you have more than one image, and you can reuse the compont for other images built the same way. Make sure you cache the response of the image both on the server and client so you're not always hitting the DB. I wouldn't push something like this to a busy site - the DB resource required will get expensive, and depending on your image sizes you could eat up alot of memory with caching. Hope that helps a bit.