Free · Fast · Privacy-first

Convert HEIC to JPG Without Installing Software

You do not need desktop software, a Microsoft Store purchase, an App Store download, a browser extension, a system codec install, or anything else that requires installation, configuration, admin rights, or licensing to convert HEIC to JPG. FixTools runs entirely inside your web browser using modern JavaScript and WebAssembly APIs that every current browser already supports out of the box. Upload HEIC files and download converted JPGs within seconds on any device with a modern browser, including Windows PCs without HEVC codec, locked-down corporate laptops, Chromebooks, Linux machines, iPhones in Safari, Android phones in Chrome, and iPads. There is no installation step at any point, no account to create, no email to verify, and no software footprint to maintain after the conversion completes.

⚡ Use Tool Now How it works

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

⚡

Zero software installation required

🔒

Works on Windows, Mac, Android, iPhone, Chromebook

✨

No account or sign-up needed

Image Tool

HEIC to JPG Converter

All processing happens in your browser — your files are never uploaded to any server.

🚀Open HEIC to JPG Converter

100% Free · No account · Works on any device

How Browser-Based HEIC Conversion Works Without Installed Software

Traditional HEIC conversion historically required dedicated desktop software because HEVC decoding is computationally intensive and was generally implemented as compiled native code calling into system codec libraries or vendor-supplied decoder SDKs. Modern web browsers have changed the picture decisively. WebAssembly, abbreviated WASM, is a binary instruction format that lets compiled C, C++, and Rust libraries run inside the browser sandbox at speeds approaching native execution, with full access to the browser's graphics, file, and computation APIs. HEVC decoder libraries originally written for ffmpeg and libheif have been cross-compiled to WebAssembly modules that load and run inside Chrome, Firefox, Safari, and Edge without any plugin, extension, or codec install. The browser fetches the WASM module on first visit, caches it aggressively for subsequent visits, and executes the decoder entirely on your local CPU.

The conversion pipeline inside FixTools works in a sequence of clearly defined steps. Your browser reads the selected HEIC file from disk into the tab's memory using the standard FileReader and Blob APIs. The WebAssembly libheif decoder parses the HEIF container structure, walks the meta box hierarchy, locates the primary image item, and decodes the HEVC-compressed payload into a raw RGBA pixel buffer in memory. The HTML5 Canvas API then draws that pixel buffer onto an off-screen canvas element of the appropriate dimensions. Finally, the Canvas toBlob method invokes the browser's built-in JPEG encoder against the canvas pixels at your chosen quality factor and produces a downloadable blob that you can save to disk. No server is involved at any step in this pipeline, and the network is only used once to load the FixTools page and its JavaScript and WebAssembly assets on the very first visit.

The privacy benefit of software-free, server-free conversion is substantial and worth understanding clearly. When you use traditional desktop software to convert HEIC, the software reads files from your local disk, processes them in local memory, and writes outputs back to your local disk; nothing leaves the machine. When you use a server-based online converter, your HEIC files are transmitted across the public internet to a third-party server, processed on infrastructure you have no visibility into, potentially logged or retained for purposes the service may or may not disclose, and the JPEG output is sent back to you over the network. With browser-based conversion using FixTools, the photos never leave the device they came from. This matters significantly for converting medical images, legal documents photographed with an iPhone, identification papers, internal corporate documents, or any personal photos you would rather not voluntarily upload to an unknown third party.

The wider implication is that software-free conversion is not a compromise compared to desktop tools but is in many ways a strict improvement. You get the same quality of output because the underlying decoder and encoder algorithms are the same. You get equal or better privacy because nothing ever transits the network. You get zero installation footprint, zero ongoing maintenance, zero licensing concerns, and zero IT approval requirements. The only real cost is that very large batches may run slower than equivalent desktop tools because browser memory budgets per tab are finite. For any normal use case involving up to a few dozen files at a time, the browser-based path is simply better than the desktop equivalent on every meaningful dimension.

WebAssembly overview and capabilities (MDN)HTML5 Canvas toBlob API (MDN)

How to use this tool

💡

Upload your HEIC files directly in the browser. No software installation, no account, no server upload. Converted JPGs download instantly to your device.

How It Works

Step-by-step guide to convert heic to jpg without installing software:

1
Open FixTools in any browser
Open Chrome, Safari, Firefox, or Microsoft Edge on whatever device you have at hand. The browser itself is the only software requirement, and any version released in the last few years includes the WebAssembly and Canvas APIs that the converter relies on. There are no plugins to install, no extensions to add, no codec packages to download, and no system permissions to grant. Just type fixtools.io into the address bar and tap through to the HEIC to JPG Converter.
2
Upload your HEIC files
Click the Upload control to bring up the system file picker, or drag HEIC and HEIF files directly onto the drop zone from a file manager window. Multiple files in a single upload are fully supported, and the picker lets you shift-click ranges or command-click individual additions to build up a batch. The files are read into the browser tab's memory but never sent across the network at any point during the upload or conversion.
3
Convert in the browser
The conversion runs entirely inside your browser using a WebAssembly build of libheif for HEVC decoding paired with the browser's built-in JPEG encoder through the HTML5 Canvas API. No files are sent to any FixTools server or any other third party at any step. You can verify this by opening browser developer tools to the Network tab and watching that no upload requests fire during a conversion session.
4
Download the JPG files
When conversion completes, download the converted JPGs individually using the per-file download buttons or hit Download All as ZIP to grab the entire batch as a single archive that preserves the original HEIC base filenames. The resulting JPG files are ready to open in any image application, attach to any email, upload to any web platform, or print at any service without any software install on either the sending side or the receiving side.

Real-world examples

Common situations where this approach makes a real difference:

Managed corporate laptop

A finance analyst at a regulated investment firm uses a locked-down corporate Windows 11 laptop where any new software install requires a formal IT ticket, security review, and group policy adjustment that typically takes a week to process. She receives eight HEIC photos from an iPhone-using client as email attachments needed for a Tuesday board pack. Using Chrome which is already installed by IT, she uploads all eight HEIC files into FixTools, converts them at quality 88 in under ninety seconds, and embeds the resulting JPGs directly into a PowerPoint deck. No IT ticket needed, no software footprint added to the corporate image, no security review required.

Chromebook user

A high school teacher using a school-provided HP Chromebook receives fifteen HEIC photos from a class of students who photographed their physical assignments on their personal iPhones over the weekend. Chromebooks run ChromeOS rather than Windows or macOS and cannot install desktop software meant for those platforms. Using Chrome on the Chromebook, the teacher navigates to FixTools, uploads all fifteen HEIC submissions in a single batch, converts them in roughly forty-five seconds at the default quality, and downloads the JPG bundle as a ZIP for grading and feedback in the school's LMS.

Privacy-conscious conversion

A solicitor preparing a property dispute case needs to convert several HEIC photos of confidential property documents taken on an iPhone during a recent site visit. The photos contain identifying client information and details about the disputed property that must not be exposed to any third party. Concerned about uploading sensitive material to an unknown online conversion service, she uses FixTools and first verifies through Chrome DevTools Network tab that no upload requests fire during conversion. Confident the processing is purely local, she runs the conversion and downloads the JPGs for inclusion in the protected legal file.

Travel laptop with limited storage

A travel photographer on a thirteen-inch ultralight laptop with a 256 GB SSD already nearly full from RAW captures cannot afford to install large image editing suites just to handle the HEIC files a collaborator sent over from an iPhone. Disk space is at a premium and another fifteen gigabytes of editor footprint is not viable. Using FixTools in Firefox on the same laptop, he batch converts thirty HEIC vacation photos totaling 95 MB into JPGs totaling 145 MB in roughly three minutes, without installing anything new and without consuming any permanent disk space for software outside of the JPG outputs themselves.

Pro tips

Get better results with these expert suggestions:

Browser-based conversion works offline after first load

After the FixTools HEIC converter page loads successfully for the first time on a given browser, all of the JavaScript bundles and the WebAssembly decoder module are cached aggressively under standard HTTP cache headers. Subsequent visits or conversions can be performed with the internet entirely disconnected, which is genuinely useful on long flights, in basement offices without cellular service, in environments with regulatory restrictions on outbound network traffic, or anywhere a connection cannot be relied upon. Keep the tab open and load HEIC files from local storage as normal.

Use browser developer tools to verify no server uploads

Open Chrome DevTools by pressing F12 or selecting Inspect from the right-click menu, switch to the Network tab, and filter the request list for XHR or Fetch requests while you upload a HEIC file to FixTools and run a conversion. You will see no outbound upload requests fire during the conversion itself, which provides direct empirical confirmation that your files genuinely stay on your device. This verification step is particularly worth doing when you plan to convert sensitive or confidential photos and want concrete evidence of the privacy guarantee.

Firefox on Windows handles HEIC without the Windows codec

Unlike Windows Photos or Adobe Photoshop, Firefox does not rely on the Windows system HEVC codec installation to decode HEIC files. FixTools running in Firefox uses its own bundled WebAssembly libheif decoder and entirely bypasses the codec requirement at the operating system level. This means FixTools works correctly even on Windows systems where the Microsoft Store HEVC Video Extensions are not installed and cannot be installed because the user lacks Store access. The same applies to Chrome and Edge on Windows.

Clear browser cache if conversion seems slow after updates

Very occasionally a browser update changes how WebAssembly modules are cached or invalidates a previously cached module, and the symptom is that conversion speed drops noticeably or the converter takes longer than usual to become ready after page load. The fix is to clear your browser cache, which is Ctrl plus Shift plus Delete in Chrome, Edge, and Firefox on Windows or Cmd plus Shift plus Delete on macOS, and then reload the FixTools page. The WebAssembly module re-downloads fresh and re-caches under the new browser cache state, typically restoring normal performance.

FAQ

Frequently asked questions

No, the converter requires only a modern web browser, which you already have on every current device by default. Chrome, Firefox, Safari, and Microsoft Edge all support the WebAssembly and HTML5 Canvas APIs that FixTools relies on for the conversion pipeline. There is no plugin to install, no browser extension to enable, no helper application to run alongside the browser, no codec package to fetch from a vendor store, and no system-level software install of any kind required at any point. The full workflow is open the browser you already use, navigate to the site, upload the HEIC files, convert them, and download the resulting JPGs.

Yes, perfectly. Chromebooks run ChromeOS rather than Windows or macOS and cannot install desktop software meant for those platforms. FixTools runs entirely inside the Chrome browser that comes pre-installed on every Chromebook, and the entire conversion pipeline lives within that single tab. Upload HEIC files using the standard ChromeOS file picker which can pull from local storage, Google Drive, or any attached USB device. Run the conversion. Download the JPGs to the local Downloads folder or save directly to Google Drive. No Android app sideload, no Linux container setup, and no developer mode is needed.

For the everyday task of converting HEIC to JPG at standard quality settings, browser-based output is bit-for-bit comparable to dedicated desktop software output. Both paths use the same underlying HEVC decoding algorithm and the same JPEG encoding algorithm at the same quality factor, so there is no quality difference inherent to the platform. The main practical limitation of browser-based conversion is memory: desktop software can address all of system RAM and handle larger individual files and larger batches without breaking a sweat, while browser tabs operate within a smaller memory budget per tab. For typical iPhone files under 50 MB each in batches up to about 50 files, the two are equivalent.

Browser compatibility is broad and stable. Chrome version 57 and later, Firefox version 52 and later, Safari version 11 and later, and Microsoft Edge version 79 and later all support the WebAssembly and Canvas APIs the converter requires. Those version cutoffs date back to 2017 or 2018, so in practical terms every browser that anyone is reasonably running today qualifies. On iOS the recommended browser is Safari because of its access to the device hardware HEVC decoder. On Android Chrome and Firefox both work well. Legacy Internet Explorer does not support WebAssembly and cannot run FixTools, but Microsoft retired IE entirely in 2022 anyway.

Yes, and this is precisely the killer feature of browser-based conversion on Windows. FixTools uses its own WebAssembly-based HEVC decoder loaded from the page itself and does not rely on the Windows system HEVC codec installation in any way. On Windows, this means conversion works in Chrome, Edge, or Firefox even when the Microsoft Store HEVC Video Extensions are not installed, which is the common state for corporate machines where the Microsoft Store is locked down by IT policy and individual users cannot purchase or install Store applications without going through an approval process that can take days or weeks to complete.

No, this is a common misconception worth correcting directly. The quality of the converted JPG output is determined entirely by the JPEG quality setting and the source HEIC fidelity, not by the conversion method or the runtime environment that performs the conversion. FixTools at quality 85 produces output indistinguishable from any professional desktop software at quality 85, because both implementations use the same standard JPEG encoding algorithm with the same quantization tables and the same DCT transform. Software-free does not mean lower quality in any sense. It simply means lower friction at the workflow level.

Server-based online HEIC converters transmit your photos across the public internet to a third-party server, where they are processed on infrastructure you have no visibility into, may be logged or retained for purposes the service does not fully disclose, and may be exposed to breaches that affect the conversion provider. Browser-based conversion runs entirely on your local device: the photos never leave the machine they came from, they never traverse the network, and there is no third-party server that could be compromised in a way that exposes them. For sensitive photos including medical images, personal documents photographed with an iPhone, identification papers, and confidential business materials, the privacy gap is significant.

Yes, and the no-install nature actually makes FixTools particularly suitable for public computer use. Library, hotel, internet cafe, and conference business center computers typically forbid users from installing any software and run on restricted accounts that lack admin rights anyway. Since FixTools requires no install, the existing browser is the only tool needed. Use a private or incognito browser window to ensure no persistent cookies or cached files remain on the shared machine after you finish, and avoid saving the converted JPGs to the public computer's local disk; instead, attach them directly to an email or upload them to your own cloud storage immediately after conversion.