Suppose you are building a small project page and want to show a circuit you photographed with your iPhone. The photo opens on the phone, but after copying it into the project and adding an image tag, you see a broken image in the browser.
If the file ends in .heic, check whether the browser or publishing tool accepts that format. A JPG copy is often easier to use. You can create it in your browser without sending the original photo to a conversion server.
Check whether the problem is the file or its path
A broken image does not tell you why it failed. Check that the path in your HTML matches the filename and that the file was deployed with the page.
Open your browser’s developer tools and look at the Network panel while reloading the page. A missing-file response points to a deployment or path problem. If the request succeeds but the image stays blank, the format is worth checking, although a damaged file can also fail to display. Try opening a converted JPG copy before changing the rest of the page.
Renaming a file from .heic to .jpg is not a conversion. That changes the name while leaving the image data in the original format. A converter must decode the HEIC image and encode a JPEG copy.
Keep the original in a separate folder. Use the converted file in your project only after you have opened it and confirmed that the picture looks right.
What happens during local conversion
An upload-based converter sends your original photo to a remote server for processing. You download the result when it finishes.
A local browser converter reads the photo you select and processes it on your computer or phone. The original stays on your device during conversion, so you avoid sending that photo to another service. You also avoid the wait for its upload, which can be noticeable on a slow connection.
The browser still needs time and memory to decode the photo and create the output. On a phone processing a large selection, that work may take longer than it would on a server. Avoiding the upload helps with transfer time; processing speed depends on the device.
Convert a JPG copy with Morphio
Morphio’s HEIC to JPG converter offers Privacy and Cloud modes. Privacy is the default for individual HEIC and HEIF images. It processes the selected images in your browser without uploading them.
Leave Privacy selected and choose the images you want to convert. Processing starts after selection. Each image has its own progress and result, and each successful input produces a separate JPG file.
Download the finished JPG. If you converted several pictures, the grouped ZIP download can collect successful results in one package. Those files remain separate images inside the archive.
Morphio places no usage cap on Privacy conversions: there is no daily or monthly quota, and they do not consume conversion credits. The practical limits are the browser and device doing the work. If a large selection causes problems, try a smaller group. You can return to the remaining photos without waiting for a quota reset.
Keep Privacy selected if you want the images to stay on your device during conversion. Switching to Cloud uploads them for server-side processing. If your source photos are inside a ZIP archive, extract them on your device before choosing the individual images in Privacy.
Add the converted file to the page
Give the downloaded file a useful name, such as circuit-board.jpg, and put it in your project’s image folder. Update the HTML to use the real filename and location.
<img src="images/circuit-board.jpg" alt="Circuit board connected to a breadboard">
Here, circuit-board.jpg is in an images folder relative to the HTML page. Change the path to match your project. Replace the alternative text with a description of your actual photograph.
Load the page through your local development server, then check it after deployment on a phone and a desktop browser. A file that exists on your computer still needs to be included in the published project. Check that it loads and that the circuit details are readable at the displayed size. If it remains broken, return to the path and network checks before converting more copies.
Check the image before publishing
JPG is a lossy format. Creating a JPG copy does not preserve every feature a HEIC file may contain, and it does not guarantee a small file. Keep the source if you might need to edit the image later.
Check the exported image’s dimensions and file size before putting it on a page. A full-resolution phone photo may be much larger than the space where you plan to show it. If it needs resizing or further compression, use a suitable editor after conversion. Do not assume that changing a format has also chosen the right web dimensions.
Local processing also does not remove metadata automatically. Morphio preserves metadata that the output format can support, so check for location information or other details you do not intend to publish. If necessary, remove them before uploading the finished JPG to your website.
Publishing the JPG on your website is a later upload to your own hosting service. Local conversion does not make that published copy private. Before deploying it, look for details in the photograph that should stay off the public page, such as a document in the background. Keep the HEIC source outside the published image folder if you are saving it only for future editing.
Leave a Reply