Dimensions often matter more than the quality slider
A 4,000-pixel photograph is usually unnecessary in a 600-pixel card. Set a maximum width close to the intended display size, allowing extra pixels for high-density displays when useful. FrameKit preserves the aspect ratio and does not upscale a smaller original. Fewer pixels usually reduce both file size and decoding work.
Choose transparency deliberately
JPG is useful for photographs with an opaque background and has no alpha transparency. PNG retains transparency and is practical for cutouts and sharp flat graphics, but can be larger. WebP can preserve transparency with a smaller file, depending on the image and quality setting. Confirm that your publishing platform accepts the chosen format.
Compare the actual download
Use Image Tools to convert the same source with two settings, then compare the output sizes and visible detail. The sample page includes the original 640×480 PNG and an actual 320×240 WebP export at 80% quality. Its reduction comes from both resizing and encoding; other images will produce different savings. Converting an already compressed JPG to PNG can increase its size.
Keep the original and check metadata needs
Browser re-encoding may change color profiles and metadata. FrameKit does not promise a forensic metadata wipe. Keep the original for archiving and verify any privacy-critical export with a specialist metadata inspection tool. Animated images and unsupported formats should be converted with a tool that explicitly supports them.