Word is compressing images even though “Do not compress images in file” is selected - why?












1















I have a document in Word 2013 and I've inserted some very high-resolution JPG images (line drawings). When I print to PDF, they look fine. However, as soon as I save the file and reopen it, the drawings are very obviously down-sampled -- the line drawings look choppy and dashed.



As noted in the question, Do not compress images in file is selected. I've also set the default output to 220dpi, but that shouldn't matter because I've asked it not to compress. (In any case, 220dpi is not good enough for me - I need this to be a high-quality print.)



I've verified & re-verified the settings, tried many convolutions, and reinserted the original pictures more times than I can count.



What could be causing this to happen? Is there some other option I am missing?










share|improve this question























  • Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

    – Romeo Ninov
    Dec 26 '18 at 16:10











  • Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

    – yosh m
    Dec 26 '18 at 19:56






  • 1





    Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

    – cybernetic.nomad
    Dec 27 '18 at 16:31











  • @cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

    – Ring
    Dec 28 '18 at 14:44
















1















I have a document in Word 2013 and I've inserted some very high-resolution JPG images (line drawings). When I print to PDF, they look fine. However, as soon as I save the file and reopen it, the drawings are very obviously down-sampled -- the line drawings look choppy and dashed.



As noted in the question, Do not compress images in file is selected. I've also set the default output to 220dpi, but that shouldn't matter because I've asked it not to compress. (In any case, 220dpi is not good enough for me - I need this to be a high-quality print.)



I've verified & re-verified the settings, tried many convolutions, and reinserted the original pictures more times than I can count.



What could be causing this to happen? Is there some other option I am missing?










share|improve this question























  • Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

    – Romeo Ninov
    Dec 26 '18 at 16:10











  • Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

    – yosh m
    Dec 26 '18 at 19:56






  • 1





    Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

    – cybernetic.nomad
    Dec 27 '18 at 16:31











  • @cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

    – Ring
    Dec 28 '18 at 14:44














1












1








1








I have a document in Word 2013 and I've inserted some very high-resolution JPG images (line drawings). When I print to PDF, they look fine. However, as soon as I save the file and reopen it, the drawings are very obviously down-sampled -- the line drawings look choppy and dashed.



As noted in the question, Do not compress images in file is selected. I've also set the default output to 220dpi, but that shouldn't matter because I've asked it not to compress. (In any case, 220dpi is not good enough for me - I need this to be a high-quality print.)



I've verified & re-verified the settings, tried many convolutions, and reinserted the original pictures more times than I can count.



What could be causing this to happen? Is there some other option I am missing?










share|improve this question














I have a document in Word 2013 and I've inserted some very high-resolution JPG images (line drawings). When I print to PDF, they look fine. However, as soon as I save the file and reopen it, the drawings are very obviously down-sampled -- the line drawings look choppy and dashed.



As noted in the question, Do not compress images in file is selected. I've also set the default output to 220dpi, but that shouldn't matter because I've asked it not to compress. (In any case, 220dpi is not good enough for me - I need this to be a high-quality print.)



I've verified & re-verified the settings, tried many convolutions, and reinserted the original pictures more times than I can count.



What could be causing this to happen? Is there some other option I am missing?







microsoft-word microsoft-word-2013






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 26 '18 at 15:59









yosh myosh m

1,82831324




1,82831324













  • Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

    – Romeo Ninov
    Dec 26 '18 at 16:10











  • Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

    – yosh m
    Dec 26 '18 at 19:56






  • 1





    Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

    – cybernetic.nomad
    Dec 27 '18 at 16:31











  • @cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

    – Ring
    Dec 28 '18 at 14:44



















  • Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

    – Romeo Ninov
    Dec 26 '18 at 16:10











  • Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

    – yosh m
    Dec 26 '18 at 19:56






  • 1





    Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

    – cybernetic.nomad
    Dec 27 '18 at 16:31











  • @cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

    – Ring
    Dec 28 '18 at 14:44

















Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

– Romeo Ninov
Dec 26 '18 at 16:10





Have you try to save, open and export to PDF and check what is the quality? Its possible Word just display low quality images to speedup the page rendering on the screen.

– Romeo Ninov
Dec 26 '18 at 16:10













Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

– yosh m
Dec 26 '18 at 19:56





Yup. No, it's not a screen display speed optimization - the pictures are really down-sampled. I can print a file to PDF - get high quality, then save, reopen and print again & it comes out lousy.

– yosh m
Dec 26 '18 at 19:56




1




1





Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

– cybernetic.nomad
Dec 27 '18 at 16:31





Have you tried looking into the XML structure of the DOCX before and after saving? (BTW, JPEGs are not meant for line drawings, you'd probably be better off saving in another format like PNG or TIFF)

– cybernetic.nomad
Dec 27 '18 at 16:31













@cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

– Ring
Dec 28 '18 at 14:44





@cybernetic.nomad, too, right. I use quite a number of visio diagrams in my documentation sets and have found that PNGs give me the best results for their size. Especially if there's any need to re-size an image.

– Ring
Dec 28 '18 at 14:44










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
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%2fsuperuser.com%2fquestions%2f1387854%2fword-is-compressing-images-even-though-do-not-compress-images-in-file-is-selec%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1387854%2fword-is-compressing-images-even-though-do-not-compress-images-in-file-is-selec%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Список кардиналов, возведённых папой римским Каликстом III

Deduzione

Mysql.sock missing - “Can't connect to local MySQL server through socket”