Initializing, please wait a moment

News

Dated updates on the formats and browser features these tools work with - every claim cites its source.

Last reviewed: 2026-07-08

Reviewed by FreetoolOnline editorial team

When a browser changes which image formats it can open, a PDF standard gains a new revision, or an operating system switches its default file type, the practical question is always the same: does anything in your own workflow need to change? Each article on this page answers that question for one specific development. Every article carries its publication date, links to the original announcements it is based on, and ends with concrete advice tied to the files you actually handle - so you can decide in a minute whether the change affects you.

Articles here stay focused on changes that touch everyday file work: image and video formats, archives and compression, PDF, browser capabilities, and privacy rules around file handling. General technology headlines are out of scope. When a story develops, the existing article is updated in place with a dated note rather than duplicated, so one URL stays the reliable reference for that topic.


How every article is checked

Each headline claim is confirmed against at least two independent sources before publication - typically one report plus a primary source such as a browser vendor's release notes, a standards body announcement, or the caniuse support tables. When reports disagree, the primary source wins, and the article says which version was verified. Direct quotes are short and attributed; everything else is written from scratch, because the useful part is not the announcement itself but what it changes for the files on your device.

  • Publication date on every article
  • A "Last reviewed" date that moves whenever the page is re-checked
  • A dated note for each later development, so you can tell how current the advice is

Why format and browser changes deserve a dated record

Most file-handling advice on the web ages silently. A guide written in 2022 will tell you that no browser opens HEIC photos, that WebP breaks in Safari, or that a new image format is "coming soon" - and none of those statements survive contact with 2026. Browser vendors ship new format support behind experimental flags first, enable it by default months or years later, and occasionally remove support they already shipped. Standards bodies publish revisions that PDF readers and archive tools adopt on their own schedules. Operating systems change default capture formats between versions, which is why a phone photo that opened everywhere last year suddenly needs converting this year.

The gap between "announced" and "usable" is where mistakes happen. A format that a browser can decode behind a flag is a preview for developers, not a safe choice for sharing files with other people. A format that one browser enables by default is still risky if the other browsers have not followed. The practical threshold is default-on support across the major browsers - and reaching that point is news worth acting on, while everything before it is news worth watching. Articles here always say which side of that line a change sits on.


What to do while a change is still settling

The safe default rarely changes: keep the formats that open everywhere as your delivery formats, and treat newer ones as an optimization you adopt when support is broad. For photos going to other people, that means JPG first - the HEIC to JPG converter covers the most common conversion, and the HEIC vs JPG vs WebP guide explains when each format earns its place. For files that are too large to send, the image compressor and the zip file creator work with formats that need no adoption watch at all. When an article here recommends changing a habit, it links the exact tool or guide for the switch, so the advice ends in a step you can take immediately rather than a development to keep an eye on.


Coverage areas

Compare four news coverage areas using the four points in this diagram.
61 news updates - pick by task

Stories are picked from the same categories the tools on this site serve. If a story does not affect at least one of those areas, it does not get an article - a small set of relevant, carefully maintained pages serves a reader far better than a fast stream of loosely related headlines ever could.

  • Image formats (JPG, PNG, WebP, AVIF, HEIC, JPEG XL) and their browser support
  • Video and audio formats
  • ZIP and archive handling, including security fixes that affect how archives should be opened
  • The PDF standard and its revisions
  • Browser and operating-system changes to file handling
  • Privacy or data-protection rules that change where files may be processed

Reviewed by the Free Tool Online editorial team · Tested in the current versions of Chrome, Firefox, Safari, and Edge before publishing. No account is needed to use any tool. Report a bug - we triage within 72 hours. · Last refreshed April 2026.

Why trust these tools

  • Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
  • No install, no sign-up. Open a tool and get a working output in seconds - nothing to download and no account to create. Tools that need heavy processing run it on our service, so even a low-powered machine gets the job done.
  • Analytics stops at the page view. We measure which pages get visited, not what you type or upload inside a tool. There is nothing to sign in to and no profile is attached to your input.
  • Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
  • Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.

Related tools:

Related guides: