I just noticed that when I download a photo from Blox, it downloads as a webp and is very small (smaller than 200KB) when the original was closer to 3MB. Is there away to maintain the photos original size as a jpg when downloading from Blox?

Are you downloading from the website or in the admin?

The easiest way to access the full res image is to open the image in the asset editor, navigate to the "Other" tab, then you will see Miscellaneous. At the bottom is "hi-res image". Click the view button, which will open the full original image in a new tab.

Thank you! That's what I needed (I knew this at one point, but I forgot).

Hi. We just noticed this change as well. Does this mean we no longer have to worry about the photo file size? We had been advised to keep these as small as possible to make sure they displayed quickly on the site. So, we have taken extra time to do that. Let us know if we can now skip this step and same time. 

Actually. I just followed the instructions. But the high-res field says none and the View button is grayed-out. See screenshothi res.png

I've run into this problem too! I can go to a different website to convert webp to jpg (for social media sites, which won't use webp) but it's a pain to have extra steps. I'm just frustrated by the change to downloading in a webp format now.

A couple of additional notes:

The "hi-res" field gets populated when an image is above a certain threshold, otherwise you can simply open the preview in the asset editor main area, right-click and save as. The threshold for what generates a hi-res instance is set in Editorial->Assets-> Settings panel (gear icon in upper right). Asset Settings -> Hi-res threshold settings. We typically recommend 1100 x 1100 here, but you could go smaller if you want. Any image with a width or height exceeding that value in pixels will generate a hi-res. Otherwise, if below, then the "full" image will be served in the preview window of the asset.

@Jesus - We recommend uploading hi-res images. We have our own image proxy/CDN system that will convert the image and generate the required sizes and formats for the device. Based on a number of factors, images may be served in jpg or webp, whichever is smaller. Sometimes webp does not actually save any filesize and it will stay in jpg. Network-wide we are averaging around 40% webp. When images are served on the front-end, we auto-size an crop the images for the container they are being served in and viewport, passing about 8 different sizes for each image in a source-set attribute on the image tag. This lets the browser select the most appropriate size for the rendered size. This also keeps bandwidth as low as possible.

@Joe. Thanks for the extra info!  

One more question: Do we still need to resize photos in articles that will be converted into a newsletter distributed through Constant Contact?