Exported JPEG file sizes

A number of my images exported to JPEG have a larger file size than the original RAW file. My export is fairly basic, quality 100, color space sRGB, no resizing, no watermark. Anyone any idea why ? I thought JPEG were supposed to be compressed.

Possibly because you are not setting an output resolution so light room is making a best interpolation.
Try setting the dimensions you want or the dimension for the long edge and use a resolution of 300ppi for printing or 72 for uploading to the web.

Similar Messages

Export to jpeg: Show jpeg file size prior to export

Photoshop save to jpeg dialog box shows the jpeg file size associated with each jpeg compression level (1 - 12). Lightroom export dialog box does not show jpeg file size. Showing the expected jpeg file size is useful when needing to limit file size while maximizing jpeg quality. For example, some email applications limit attachment file size; some photo hosting sites (e.g., Zenfolio) limit file size to 12mb. If I export a cr2 file at 100 quality, it may result in a file size of 14mb. However, I cannot determine this until after I export. Then I may try 90 quality and find that the resulting file size is only 8mb. So, I try 95 quality, and get a 12.5mb file. This iterative process is a waste of time. I need to se the file size resulting from each jpeg quality setting in the export dialog box.

I have tried trashing the plist file. The files look fine through the media manager when copied to the other profile. They look like they are suppose to. The small videos also look fine when played on that computer. Unfortunately our other mac pro computer doesn't have final cut so i can't open and play proress files and my laptop, due to the extreme resolution can't be played on my laptop with final cut studio installed. Tomorrow i'm going to install the proress decoder on the one mac pro to check the files and make sure the self contained is checked but i'm almost positive on that. Other than nuking the profile i don't know what else to do. This is really weird.

Aperture exports jpeg files larger than original RAW files

Can anyone tell me why a RAW file (10.6mb), when exported as a jpeg (10.8mb) from Aperture ends up larger than the original RAW file. The same RAW file when opened and then saved as a jpeg (6.4mb) in Photoshop is a lot smaller. The photo dimensions and resolution are the same in both saved files (34.5mb open file 300dpi 4256 x 2831 pix). I have tried this on several photos, all with similar results. For information I am saving the photos in both Photoshop and Aperture at 300dpi, original size and at a quality setting of 12. In these examples/tests I have done no work to the photos, obviously the file sizes increase after work has been carried out on the photos (in both Ps & Aperture)
Almost doubling the size of saved jpegs has a massive implication on my library and may be one reason to consider Adobe Lightroom as this gives similar jpeg file sizes as Photoshop, i.e. almost half the size of the original RAW file
Reducing the quality setting on saved jpegs is an obvious way to reduce file size, but not answering the question of the considerable discrepancy when saving to the same quality in different software
Is this a feature of Aperture and nothing can be done about it ? I would prefer to use Aperture but cannot cope with the large jpeg sizes !
Any comments would be much appreciated - thank you
Nick

Think you might be right Allen - The 12 quality saved jpegs seem to be pretty high quality, closer to the original than maybe the files saved in Ps at quality 12. I have just run an identical set of processing actions on all the files in Photoshop and the jpegs previously saved in Aperture at 12, 11 and even 8 quality settings seem to be better than the same files saved at 12 in Ps
Bizarrely the file size drops from 10.6mb at quality setting 12 in Aperture, to 3.2mb when saved just one notch down at quality setting 11 in Aperture. That is a massive drop, esp considering the next one down, saving at quality 10 results in a 2.8mb file
rw just ran some checks and tests on the file export settings and file sizes in Aperture, on a file I sent him, and we get the same results. So at least my version of Aperture is not up the wall !!
Would be useful to have the explanations from Apple as to the vast variance in settings and file sizes, but I guess we will just have to keep guessing - and buying more and more hard drives for all the large files
I am considering keeping the RAW originals in future, and I suppose in this case I need only save smaller jpegs, and issue at whatever size they are needed at the time - just needs a bit of planning to look after an ever increasing collection, which is about to have two sets of images added at a time now. Added to the already amassed 80 000 images at last count !)
Thanks
Nick

Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

Raws, even if not compressed, Sould be smaller than a 24-bit Tiff, since they have only one bitplane. My T3i shoots 14 bit 18MP raws and has a raw file size of 24.5 MB*. An uncompressed Tiff should have a size of 18 MP x 3 bytes per pixel or 54 MB.
*There must be some lossless compression going on since 18 MP times 1.75 bytes per pixel is 31.5MB for uncompressed raw.

Can I resize photos and reduce JPEG file sizes by using Photpshop Elements?

Can I resize photos and reduce JPEG file sizes by using Photpshop Elements?

Go to Image>Resize>image size.
For purpose of web posting, go to File>save for web.

Why Is "Export Small File Size" Large?

Hi, I work in CS3. Out of 100 brochures, I have two brochures that will not export to a small file size PDF. The settings for export are all the same. What else should I be looking for? The sizes are usually 1 MG. These particular 2 brochures are 5 - 6 MG. What can I look for to correct this?
Thanks

Small size is very dependent on the contents being exported to PDF. Images are readily compressed. Text and vector data isn't. Thus, if your content is primarily text and vector, it is very unlikely that the content can be compressed signficantly more via change of settings.
Another factor that can relate to image compression is use of any duotones that use spot colors. Such images cannot be JPEG-compressed, only ZIP-compressed.
- Dov

Lightroom 4.1 exported JPEG files are not recognized by Apple Preview App

I just started using Lightroom 4.1 Trial version (coming from Aperture). I exported JPEG versions of some images using an ICC profile. On my iMac running Lion 10.7.5 the pictures do not show a thumbnail, the file on the desktop just shows "JPEG". I could not open the file with the Preview App, but I am able to open it with DPP (Canon software)? Also the file shows that it has 0 x 0 dimentions when I click Get Info even though it is about 25 Megs in size?
The message I get is
"The file “Edit-739820120223Canon EOS 7D.jpg” could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize."
Does anyone know why this is hapening?
Is it a know issue between Adobe and Apple?
Is there a fix for this?
Thanks for help in advance.

25MB is quite a large filesize for a JPG, and this might be either quite a lot of pixels saved at a very "high" quality (not very much compressed), or it may be an extremely large number of pixels saved with medium compression.
While the technical spec of the JPG format imposes an absolute limit on maximum width and height pixel dimensions, some software employs a lower limit above which it considers the file to be invalid. Different programs, different limits, sometimes.
I have encountered this (for example) with pano stitched images using the full resolution of a large number of component shots - where JPG output could not be made, or if made, could not even be viewed as a whole by my standard image viewer (though TIFF was still OK even at still larger sizes).
If Lightroom has been set to a large printed size AND to a high ppi resolution, it is easy to get into very high numbers and very large output files. One should IMO at least question the utility and benefit of using very high ratios of upsampling from a standard digital photo - which may happen in some cases as a result of using the same output settings regardless, when spreading the same data across both small and large scales. If the file that was imported into LR really does provide an unusually high number of pixels expressing lots of detail, then that will better deserve such a capacious output file. Otherwise, each part of the file may merely show a very highly detailed representation, of a very blurry nothing-much-in-particular.
If the JPG has exceeded the viewer's size limits, a reported width and height of 0 may represent an error message, in effect - not actual reality.
regards, RP

JPEG file sizes compared to PS.

Hi there folks
I've noticed that the file sizes when exporting from Aperture2 to jpg are considerably different to the same files exported from Photoshop.
For example one image which was set to jpeg compression level 5 with DPI of 240 came out as 1.4mb whereas in photoshop the same image came out as 500kb.
Has anyone else noticed this and are there any settings I can check to see if there is something causing this?
Thanks for your help
Graeme

Yeah it seems to vary from about 70-100% bigger depending on the image. I was wondering if it was something to do with the metadata that's included. I always include my metadata because I am shooting for a news agency, but maybe it's the way that it stores it in the file????
I want to keep using Aperture as much as possible because I have the uberupload plugin as well and it means I can fire stuff straight through to the agency from aperture by FTP without any other apps and makes my workflow a lot quicker.
Has puzzled me.

Export constrain file size

The lab my client uses doesn't like to handle jpegs larger than about 2MB. OK, that's their rule and I have to make it work.
In PhotoShop, when I converted to jpeg I could see how large a file it was going to produce. In LightRoom I don't know how to do that. I can choose a quality, which isn't measured in anything. And I can enter a dpi, which shouldn't make any difference if the pixel count is unchanged. There's no way to sort by size. So I guess and export them all, then check the sizes and go back again and re-export the files that are too large. Very Clumsy.
Can anyone advise me how to get these Canon 5D files to convert to jpegs at around 2MB?
-wick

Through trial and error (no help from LightRoom), I decided to contrain the file size to within a 2K by 2K pixel rectangle. This gives me roughly the right file size. thanks to all for your suggestions. In the end, of course, I either have to downsize the image or raise the compression to around 60 (as Ian suggested). In the end, assuming a print size no larger than 8 x 10, do you think the better solution is to downsize or upcompress?
-wick
PS: Has anyone else come across the bug mentioned in my second post, where exporting the same file over and over leads to the wrong file getting exported? Maybe LightRoom just got bored?

JPEG file size

I have been using both Lightroom and Aperture, and have noticed that Aperture's JPEG exports are much larger files than those produced by Lightroom. I have been using what are seemingly equivalent JPEG quality settings (say, Aperture's #8 out of 12, and Lightroom's #60 out of 100).
Why is this so?
Thanks.

You would have to run a test with
i identical
images because a Jpeg's file size will vary considerably dependent upon the subject matter.
If there is a significant difference between two identical files, both saved at maximum quality, it will be because one program is saving more metadata than the other.

Exporting reducing file sizes

Im using a version of aperture 2 at the moment and i have noticed that when i export my jpegs at original size they are only coming out half the size into my destination folder - i shoot in HQ jpeg, original size straight out of camera is 5-6mb. When i import them into aperture they still show as 5-6mb in the metadata. Then when i export them - always at original size I have checked and checked this - they are reducing to 2-3 mb in the destination folder. In photoshop these smaller files are measuring approx 4000x3000 pixels and when i then save them as high res jpegs out of PS they are jumping back up to the initial 5-6mb. I am confused. Dont want to be doing any more destruction than i need to.

Check your export settings. When you see "JPEG - Original Size" as the export preset, that is just the title of the preset. Choose edit and see what the actual settings are for "JPEG - Original Size"
And I'm looking at Aperture 3 when I say that. Can't remember if it's the same with 2.

Exported media file size issues Sometimes one size, Sometimes another without making any changes in FCPX?

Hi there
I'm having some strange issues with files sizes from
Share>Export Media
I'm not changing anything about the video (just moving an audio track forwards and backwards ever so slightly to try and get it to the correct timing), nor am I changing anything about the way I export the video.
I am always using the EXACT same settings
Sometimes finder states my video is 1.15GB, sometimes its states its 3.8GB
But then when I close Finder down and then go back into Finder again to find the file it states its gone from 1.15GB to 3.8GB
I'm not sure if this is a error with my system or Final Cut Pro X?
By the way I'm running 10.0.5
Thanks

Bob,
Well, the issue has gone to press and I have upgraded to Snow Leopard and CS5. Initial tests show that the problem still exists, and that it is related to the XML tags. The problem occurs both with legacy (CS4) documents and documents created from scratch in CS5. As I mentioned before, it only seems to happen when overrides are applied to paragraph styles.
Here is a sidebar as exported from InDesign. Overrides were applied to the two headlines to modify color, point size and baseline shift:
The file with XML tags, packaged and opened in InCopy CS5:
The same file with XML tags removed, packaged and opened in InCopy:
OK. Now is when things start to get really interesting.
I thought perhaps that exporting the InDesign file as an IDML document, then reopening it, might perhaps fix the problem. But, no. In fact, when I reopened the IDML file in InDesign, the font styles were broken in _exactly_ the same places as they were in InCopy. Apparently, whatever problem InCopy is having with the XML tags is being duplicated by the IDML export. (Do these processes share the same file format?)
For example, here is a title page from the magazine as a screen grab in InDesign. Overrides were applied to the top headline on a line-by-line basis:
The same file, exported as an IDML file and reopened in InDesign:
As with InCopy, when the XML tags are removed, the IDML file reopens in InDesign just fine. Unfortunately, removing the XML tags is not a option. We need them to repurpose the content after it goes to press.
This is a real bug, and for us it's a serious one. I'm surprised it hasn't come up before. Is there any way to draw this to Adobe's attention? I'd be more than happy to share any of these files if that would help.
Steve

Problem exporting '.txt' file size 23 KB and '.zip' file size 4 MB

I am using Apex 3.0 version screen to upload '.txt' file and '.zip' file containing images.
I can successfully export '.txt' file and '.zip' file containing images as long as '.txt' file size is < 23 KB and '.zip' file size < 4 MB from database table 'TBL_upload_file' to the OS directory on the server.
processing of Larger files (sizes 35 KB and 6 MB) produce following Error Message.
‘ORA-21560: argument 2 is null, invalid or out of range’ error.
Here is my code:
I am using following code to export Documents from database table 'TBL_upload_file' to the OS directory on the server.
create or replace procedure "PROC_LOAD_FILES_TO_FLDR_BYTES"
(pchr_text_file IN VARCHAR2,
pchr_zip_file IN VARCHAR2)
is
lzipfile varchar(100);
lzipname varchar(100);
sseq varchar(1000);
ldocname varchar(100);
lfile varchar(100);
-- loaddoc (p_file in number) as
l_file UTL_FILE.FILE_TYPE;
l_buffer RAW(32000);
l_amount NUMBER := 32000;
l_pos NUMBER := 1;
l_blob BLOB;
l_blob_len NUMBER;
l_file_name varchar(200);
l_doc_name varchar(200);
a_file_name varchar (200);
end_pos NUMBER;
begin
-- Get LOB locator
SELECT blob_content,doc_name
INTO l_blob,l_file_name
FROM tbl_upload_file
WHERE DOC_NAME = pchr_text_file;
--get length of blob
l_blob_len := DBMS_LOB.getlength(l_blob);
-- save blob length to determine end position
end_pos:= l_blob_len;
-- Open the destination file.
-- l_file := UTL_FILE.fopen('BLOBS','MyImage.gif','w', 32767);
l_file := UTL_FILE.fopen('BLOBS',l_file_name,'WB', 32760); --use write byte option supported in 10G
-- if small enough for a single write
IF l_blob_len < 32760 THEN
utl_file.put_raw(l_file,l_blob);
utl_file.fflush(l_file);
ELSE -- write in pieces
-- Read chunks of the BLOB and write them to the file
-- until complete.
WHILE l_pos < l_blob_len LOOP
DBMS_LOB.read(l_blob, l_amount, l_pos, l_buffer);
UTL_FILE.put_raw(l_file, l_buffer);
utl_file.fflush(l_file); --flush pending data and write to the file
-- set the start position for the next cut
l_pos := l_pos + l_amount;
-- set the end position if less than 32000 bytes, here end_pos captures length of the document
end_pos := end_pos - l_amount;
IF end_pos < 32000 THEN
l_amount := end_pos;
END IF;
END LOOP;
END IF;
--- zip file
-- Get LOB locator to locate zip file
SELECT blob_content,doc_name
INTO l_blob,l_doc_name
FROM tbl_upload_file
WHERE DOC_NAME = pchr_zip_file;
l_blob_len := DBMS_LOB.getlength(l_blob);
-- save blob length to determine end position
end_pos:= l_blob_len;
-- Open the destination file.
-- l_file := UTL_FILE.fopen('BLOBS','MyImage.gif','w', 32767);
l_file := UTL_FILE.fopen('BLOBS',l_doc_name,'WB', 32760); --use write byte option supported in 10G
-- if small enough for a single write
IF l_blob_len < 32760 THEN
utl_file.put_raw(l_file,l_blob);
utl_file.fflush(l_file); --flush out pending data to the file
ELSE -- write in pieces
-- Read chunks of the BLOB and write them to the file
-- until complete.
l_pos:=1;
WHILE l_pos < l_blob_len LOOP
DBMS_LOB.read(l_blob, l_amount, l_pos, l_buffer);
UTL_FILE.put_raw(l_file, l_buffer);
UTL_FILE.fflush(l_file); --flush pending data and write to the file
l_pos := l_pos + l_amount;
-- set the end position if less than 32000 bytes, here end_pos contains length of the document
end_pos := end_pos - l_amount;
IF end_pos < 32000 THEN
l_amount := end_pos;
END IF;
END LOOP;
END IF;
-- Close the file.
IF UTL_FILE.is_open(l_file) THEN
UTL_FILE.fclose(l_file);
END IF;
exception
WHEN NO_DATA_FOUND THEN
RAISE_APPLICATION_ERROR(-20214,'Screen fields cannot be blank, Proc_Load_Files_To_Fldr_BYTES.');
WHEN TOO_MANY_ROWS THEN
RAISE_APPLICATION_ERROR(-20215,'More than one record exist in the tbl_load_file table, Proc_Load_Files_To_Fldr_BYTES.');
WHEN OTHERS THEN
-- Close the file if something goes wrong.
IF UTL_FILE.is_open(l_file) THEN
UTL_FILE.fclose(l_file);
END IF;
RAISE_APPLICATION_ERROR(-20216,'Some other errors occurred, Proc_Load_Files_To_Fldr_BYTES.');
end;
I am new to the Oracle.
Any help to modify this scipt and resolve this problem will be greatly appreciated.
Thank you.

Ask this question in the Apex forums. See Oracle Application Express (APEX)
Regards Nigel

Jpeg file size 6D vs 60D

Hi all,
Being a bit newer at all this I'm sure there is something I don't know that I don't know  which would answer this:
Been taking some identical test shots on my new 6D and my old 60D to compare. Jpeg only for now, same "quality" setting.    I noticed that the file sizes of the pictures on the 60D were larger than the 6D's. I would have thought that with a larger sensor and roughly 2mp more the 6D's would have been the larger, or at least the same. Some of the 60d's were almost 3-4 mb larger.
Lenses if it matters: 6D 24-105L kit, 60D EFS 15-85 IS.   ISO was the same in some, apetures pretty close in most.
What am I missing?

Thanks for the response.
Good point on the noise reduction, I'll check those settings to see if they are on the same setting.
I tried to frame the shots exactly the same, using only the center AF point focused on the same point for both.   Got them pretty close.
I came across a 6D review that had a table showing the raw file sizes for various cameras at various ISO's, and it showed the 60d and 6d pretty similar (still not understanding why given larger sensor and 2 more mpixel) . The 60D's got larger at the higher ISO. I am guessing increased noise may be the reason?

Exported mp3 file size is huge!

Does anyone know how to control the size of an exported song? For a 5 minute track I'm getting a 60Mb MP3!! I'm guessing this is done by setting the a different bit rate for the exported song but can't find any options in Garageband to do this.
With such huge file sizes it makes it difficult to share the song through my website.

No, you're not getting a 60 MB MP3, but a 60 MB AIFF file, and that's the regular size for uncompressed audio files. The bitrate in GB is fixed, and you wouldn't want to change it. Instead, convert the file into an MP3 or AAC in iTunes.
(Come back if you need help with doing that.)

Exported JPEG file sizes

Similar Messages

Maybe you are looking for