Webp images on different browsers











up vote
0
down vote

favorite












I have a problem. In my HTML pages I have a lot of Webp images that I can visualize only using Google Chrome. With other browsers like Mozilla, Explore or Safari I can't see them.



Is there a solution? Maybe without change every image's extension (cause they are a lot)?



Thanks










share|improve this question
























  • Related - Detecting WebP support
    – vsync
    Nov 8 at 12:21















up vote
0
down vote

favorite












I have a problem. In my HTML pages I have a lot of Webp images that I can visualize only using Google Chrome. With other browsers like Mozilla, Explore or Safari I can't see them.



Is there a solution? Maybe without change every image's extension (cause they are a lot)?



Thanks










share|improve this question
























  • Related - Detecting WebP support
    – vsync
    Nov 8 at 12:21













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a problem. In my HTML pages I have a lot of Webp images that I can visualize only using Google Chrome. With other browsers like Mozilla, Explore or Safari I can't see them.



Is there a solution? Maybe without change every image's extension (cause they are a lot)?



Thanks










share|improve this question















I have a problem. In my HTML pages I have a lot of Webp images that I can visualize only using Google Chrome. With other browsers like Mozilla, Explore or Safari I can't see them.



Is there a solution? Maybe without change every image's extension (cause they are a lot)?



Thanks







html webp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 8 at 11:26









vsync

44.1k35154214




44.1k35154214










asked Nov 8 at 11:22









Marco P

124




124












  • Related - Detecting WebP support
    – vsync
    Nov 8 at 12:21


















  • Related - Detecting WebP support
    – vsync
    Nov 8 at 12:21
















Related - Detecting WebP support
– vsync
Nov 8 at 12:21




Related - Detecting WebP support
– vsync
Nov 8 at 12:21












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










You need to fallback to a supported image format. here's an example using the <picture> element:



<picture>
<source srcset="image.webp" type="image/webp">
<source srcset="image.jpg" type="image/jpeg">
<img src="image.jpg" alt="">
</picture>


You did not specify the very important information - are you using the images as <img> elements or a CSS backgrounds?



If the images are used in CSS then you can use Modernizr's .no-webp class name to target non-support browsers and serve a non-webp format instead:



.no-webp .elementWithBackgroundImage {
background-image: url("image.jpg");
}



This article has good information you can use






share|improve this answer























  • So I must change every image extension, right?
    – Marco P
    Nov 8 at 11:32










  • I use <img src="....webp">
    – Marco P
    Nov 8 at 11:34










  • @MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
    – vsync
    Nov 8 at 11:34












  • Ok thank you very much, it will be a long work for me ahah
    – Marco P
    Nov 8 at 11:36













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206746%2fwebp-images-on-different-browsers%23new-answer', 'question_page');
}
);

Post as a guest
































1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










You need to fallback to a supported image format. here's an example using the <picture> element:



<picture>
<source srcset="image.webp" type="image/webp">
<source srcset="image.jpg" type="image/jpeg">
<img src="image.jpg" alt="">
</picture>


You did not specify the very important information - are you using the images as <img> elements or a CSS backgrounds?



If the images are used in CSS then you can use Modernizr's .no-webp class name to target non-support browsers and serve a non-webp format instead:



.no-webp .elementWithBackgroundImage {
background-image: url("image.jpg");
}



This article has good information you can use






share|improve this answer























  • So I must change every image extension, right?
    – Marco P
    Nov 8 at 11:32










  • I use <img src="....webp">
    – Marco P
    Nov 8 at 11:34










  • @MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
    – vsync
    Nov 8 at 11:34












  • Ok thank you very much, it will be a long work for me ahah
    – Marco P
    Nov 8 at 11:36

















up vote
0
down vote



accepted










You need to fallback to a supported image format. here's an example using the <picture> element:



<picture>
<source srcset="image.webp" type="image/webp">
<source srcset="image.jpg" type="image/jpeg">
<img src="image.jpg" alt="">
</picture>


You did not specify the very important information - are you using the images as <img> elements or a CSS backgrounds?



If the images are used in CSS then you can use Modernizr's .no-webp class name to target non-support browsers and serve a non-webp format instead:



.no-webp .elementWithBackgroundImage {
background-image: url("image.jpg");
}



This article has good information you can use






share|improve this answer























  • So I must change every image extension, right?
    – Marco P
    Nov 8 at 11:32










  • I use <img src="....webp">
    – Marco P
    Nov 8 at 11:34










  • @MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
    – vsync
    Nov 8 at 11:34












  • Ok thank you very much, it will be a long work for me ahah
    – Marco P
    Nov 8 at 11:36















up vote
0
down vote



accepted







up vote
0
down vote



accepted






You need to fallback to a supported image format. here's an example using the <picture> element:



<picture>
<source srcset="image.webp" type="image/webp">
<source srcset="image.jpg" type="image/jpeg">
<img src="image.jpg" alt="">
</picture>


You did not specify the very important information - are you using the images as <img> elements or a CSS backgrounds?



If the images are used in CSS then you can use Modernizr's .no-webp class name to target non-support browsers and serve a non-webp format instead:



.no-webp .elementWithBackgroundImage {
background-image: url("image.jpg");
}



This article has good information you can use






share|improve this answer














You need to fallback to a supported image format. here's an example using the <picture> element:



<picture>
<source srcset="image.webp" type="image/webp">
<source srcset="image.jpg" type="image/jpeg">
<img src="image.jpg" alt="">
</picture>


You did not specify the very important information - are you using the images as <img> elements or a CSS backgrounds?



If the images are used in CSS then you can use Modernizr's .no-webp class name to target non-support browsers and serve a non-webp format instead:



.no-webp .elementWithBackgroundImage {
background-image: url("image.jpg");
}



This article has good information you can use







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 8 at 11:35

























answered Nov 8 at 11:29









vsync

44.1k35154214




44.1k35154214












  • So I must change every image extension, right?
    – Marco P
    Nov 8 at 11:32










  • I use <img src="....webp">
    – Marco P
    Nov 8 at 11:34










  • @MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
    – vsync
    Nov 8 at 11:34












  • Ok thank you very much, it will be a long work for me ahah
    – Marco P
    Nov 8 at 11:36




















  • So I must change every image extension, right?
    – Marco P
    Nov 8 at 11:32










  • I use <img src="....webp">
    – Marco P
    Nov 8 at 11:34










  • @MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
    – vsync
    Nov 8 at 11:34












  • Ok thank you very much, it will be a long work for me ahah
    – Marco P
    Nov 8 at 11:36


















So I must change every image extension, right?
– Marco P
Nov 8 at 11:32




So I must change every image extension, right?
– Marco P
Nov 8 at 11:32












I use <img src="....webp">
– Marco P
Nov 8 at 11:34




I use <img src="....webp">
– Marco P
Nov 8 at 11:34












@MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
– vsync
Nov 8 at 11:34






@MarcoP - well, you need 2 formats for sure. You can also use 3rd party image hosting service such as Cloudinary, which can auto-detect browser support and serve the right format to the user
– vsync
Nov 8 at 11:34














Ok thank you very much, it will be a long work for me ahah
– Marco P
Nov 8 at 11:36






Ok thank you very much, it will be a long work for me ahah
– Marco P
Nov 8 at 11:36




















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206746%2fwebp-images-on-different-browsers%23new-answer', 'question_page');
}
);

Post as a guest




















































































Popular posts from this blog

鏡平學校

ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

Why https connections are so slow when debugging (stepping over) in Java?