Does Brave support JPEG XL or JXL, since Google has now axed it from Chromium

Does Brave support JPEG XL image file format, now that Google has axed it from chromium version 110?

1 Like

Maybe Brave does. Not sure. @Mattches @steeven please confirm

I don’t believe we will — we’ll likely match what Chromium supports in this case. Apologies for the inconvenience.

Well that’s too bad. Here’s hoping that it may come back in the future chromium updates

So you choose to let Google misuse their monopoly and kill a format that has all the reason to live. Big companies like Intel, Adobe, Facebook, Nvidia and more are asking Google to reconsider and question the logic behind this decision. I don´t think it´s a coincident that Google is pushing a competing format which isn´t being backed and endorsed like JPEG XL is, so this is what Google does. Even Google employees are asking the team to reconsider…

Brave should be focues on going against the monopoly keeping users free from the chains of monopoly companies, but instead it seems you are just doing whatever Google dictates.

It´s pretty obvious that the browser monopoly is not good for technology.

It´s incredibly disappointing that Brave just shrugs this off. :frowning:

Not unless companies and developers speak up and use leverage against Google. It would be pretty easy for companies to publically recommend FireFox (or Brave if they didn´t just comply to Google´s monopoly). It would be easy for companies to show a message that says Chrome does not support the format and ask users to switch browser to make sure the webpage renders correctly (by using JPEG XL on non-user critical assets). As a protest and to show Google that they can´t just use their monopoly to kill competing standards despite a large following of many big relevant companies and services asking for it. If all the big services did this they would be able to push a certain percentage off Google´s browser and make a certain dent in Google´s user base. What if Brave was one of these recommended browsers?

Yes, it´s “just a format”. But it´s not really just a format. It´s about something bigger than this. And it´s an actual good standard as well. It has features webp will never have. It´s an open and royalty free format that losslessly compresses old JPEGs into JPEG XL. It supports gradual loading, animation, lossless mode, alpha etc. and is a solution to generation loss which is becoming an increasingly big problem. It´s just a promising format and we also benefit from having alternatives. Monopolies never end well.

This behaviour from Google is anti-competitive and definitely not the first time they´ve used a service or search engine to try to kill competing companies. Google is no small-time player, they have too much power and as a monopoly they actually have a responsibility beyond their own interests.

By allowing Google to do this, we are enabling exactly what we are trying to avoid with forks like Brave. And the fact that Brave doesn´t firmly agree with this has me worried if Brave really is the browser I should be supporting.

We need FireFox more and more as time goes on.

We need Brave as well. So please be brave and don´t let Google dictate what you do…

This is honestly disappointing to hear. Google killing JPEG XL is another Manifest V3 fiasco: most people don’t support it, but because Google almost has a monopoly on the browser market, it’s something most people will comply with because they almost have no choice.

As saar (rudely) pointed out, big companies like Adobe (responsible for Lightroom and Photoshop) and Facebook (who owns Instagram, literally the social media for pictures) clearly disagree with this decision. Chromium developers gave uncredited and blatantly false reasons, and when people pointed it out, they ignored and went ahead anyways. It may not because they’re trying to push WebP, but rather they’re trying to push AVIF on behalf of the Alliance For Open Media. For an alliance that cares so much about open media, they are being close-minded and anti-competitive.

I hope the Brave team will reconsider this decision and not only keep JPEG XL, but enable it by default. Brave has always been one of the browsers to stand up against Google and Chromium when they make decisions that are not in the users’ best interests; one of the reasons I continue to use Brave after so long. JPEG XL is not only beneficial for web developers, but also for every day users, but they wouldn’t know because JPEG XL was never given a chance. Please keep the web open!

Hi, can you point to where you think I was being rude? It was definitely not my intention. It would be helpful to know so that I can avoid being misunderstood in the future.

I agree with your post. Good to see that there are others that care about this.

Yes, I just noticed in your first post you came off a little blunt. That’s where I was perceiving the rudeness. But I still agree with all of your points. I probably just would’ve said them differently hahahaha.

I think that´s a fair point, I can see how it can be interpreted in different ways and it should´ve been worded differently. I suppose I get very passionate at times so that comments get too consise and direct. Communitcating over text can be interpreted in many ways, especially when I don´t have the habit of using emoticons.

Brave can honestly do what they want and I understand that they cannot rectify every incident like this caused by the Chromium project. Though, as far as I know, a lot of the (JPEG XL implementation) work wasn´t even done by Google but rather other developers and volunteers. I do think Brave should invite the community to develop open-source implementation for it and enable it through a flag until it works well enough to be enabled by default. If that actually happened, Google would, by their own words, have no reason to exclude it in the Chromium project (as their reasoning heavily leans on the maintaining side of things).

At the same time I will be very disappointed if companies and individuals with (and without) influence stay silent about this and by extension let it happen. Google can definitely be pressured into not behaving this way, but that requires people to actually protest this and also take actions that leads to Google having to change their mind.

Why should Google care? Because as a monopoly they have power over the market/competition and the public space that they should not have. It is different when they actually can rewrite history to this extent, especially when they are doing it, and have done repeatedly in the past, to stifle competition.

Hopefully this won´t kill off the format.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.