If you are a Capture One user, you might be wondering how you can properly resize your images for web use, so that the resulting files look great on any platform. Exporting full-size images from your high-resolution camera is typically not ideal, because you end up with very large images that are hard to work with. With most online platforms automatically down-sizing and compressing large images, you might end up with photos that simply do not look good. For this reason, it is a good idea to find out the best resolution for each platform, then export your images in that size. In this article, I will show you the proper way to resize images in Capture One using two different methods.
Capture One Image Resizing Workflow
Capture One has two methods to effectively resize images. The first method involves creating a “Process Recipe” (which is basically a preset with particular values), then reusing that recipe every time you need to export an image. The second method involves exporting an image variant in JPEG format, which you can invoke through a dialog each time you need to export an image. My personal preference is the former since I can batch export many images at once without changing any settings. I will go through both of these methods in this article. Here is my simplified workflow process for resizing and exporting images from Capture One:
- Import images into Capture One
- Make necessary adjustments to the image(s) I want to resize
- Apply sharpening to the full-sized image via the Details Tool
- Create a Process Recipe for specific output resolution and set up output sharpening
- Preview output sharpening via the Proofing tool
- Select image(s) I want to export, then use the “Process” shortcut to export them using the previously-created Process Recipe
This method takes a bit of time to set up properly, but once you do it, exporting images is a breeze.
Capture One Image Resizing Process: Exporting with a Process Recipe
- Select an image you want to export out of Capture One Pro, then click on the Output tool to reveal a number of options, including “Process Recipes”, “Output Location”, “Output Naming”, and “Process Summary”. The tool should look like this:
Let’s go over each section and create a Process Recipe.
- Start out by creating a new Process Recipe for the resolution you need to export your images in. Click on the “+” sign under the “Process Recipes” dropdown. A new “Untitled Recipe” will pop-up right above. Click on it and rename it to something more descriptive. I typically export my JPEG images at 2048 pixel long resolution, so that’s what I am going to use as a name for my recipe. I will call it “JPEG sRGB 2048px for web”, as shown in the above screenshot. Make sure that the new recipe remains checked and everything else is unchecked. This will only enable the new preset we created for exporting.
- Next, click on the “Process Recipe” drop-down and expand its options. Here, you will have a few very important tabs that you will need to configure. Under the “Basic” tab, you will be specifying the image format and all the relevant options, including image resolution. Here is what I set up mine to:
I set up my output format to JPEG, 80% quality, sRGB color space profile, and 2048 pixel-long resolution. The “Resolution” field is only relevant for printing, so you can ignore this setting if you are exporting for the web (this value can be overridden during the printing process anyway). I do not want my exported images to be opened after they are exported, but if you would like to see it with your image viewer, you can set it up under “Open With”.
Click on the “File” tab to select the output folder where your images will be exported to. Here, you can set up all kinds of presets to create subnames and subfolders. Since there is a separate “Output Location” drop-down further down that allows you to select file destination and create sub-folders, I would recommend leaving these fields empty and setting up “Output Location” as the Root Folder:
The next “Adjustments” tab is very important because this is where we will set up output sharpening. Make sure to pick “Respect crop” under the “Crop” setting, so that Capture One does not output the original uncropped image. Under “Sharpening”, make sure to select “Output Sharpening for Screen” when exporting images for the web. Set the desired Amount, Radius, and Threshold:
If you are wondering which settings are best to use here, the answer is “it depends”. Unlike Lightroom that only gives you three output sharpening options, Capture One gives a lot more flexibility. First of all, the output sharpening settings are applied on top of the existing sharpening that you have already applied to the full-size image, so you have to be careful with what you pick. So how can you tell which settings are best without seeing the end result? This is where you utilize the “Recipe Proofing” tool (the icon that looks like eyeglasses):
You can also invoke the Recipe Proofing tool using the SHIFT + CTRL + \ shortcut (SHIFT + CMD + \ on Mac). Once Recipe Proofing is enabled, you will see the image with “Proofing” text over it. Note that the image will be resized to the exact resolution that you are exporting the image in. From here, make sure you zoom in to 100% or 200% of the image (use the + on the loupe tool or press CTRL + (CMD + on Mac) to see the image up close:
Now that you are looking at the actual output, it is time to adjust your sharpening settings. For the image above, I wanted to sharpen all the small details, including some of the rocks in the foreground. I picked 120 for “Amount”, 0.6 for “Radius”, which looked great. To make sure that sharpening does not add much noise all over the image, I bumped up “Threshold” to 0.5.
The Recipe Proofing tool is a great way to look at the end result. Once you are done, your exported sharpened image should look identical to how it appeared in this window!
Next, navigate to the “Metadata” tab. Here, unless you want your exported image to contain sensitive data such as your GPS coordinates and camera settings, you should just uncheck most of the settings. For my recipe, I unchecked everything other than “Copyright”:
Lastly, the “Watermark” tab is there for adding a watermark to your images. I typically don’t add any watermarks to my images, but if you want to do that, you can do it from here.
- The “Output Location” drop-down is for picking your output folder and subfolder (if you want to set one):
- The last two drop-downs are “Output Naming” and “Process Summary”:
Since I name my images during the image import process and want my exported files to have the same corresponding file name, I do not change them here and leave “Image Name”. However, if you prefer to rename your images when they are exported, you can set up a preset under “Format”. The sample file name is displayed below, as shown in the above screenshot.
Lastly, the “Process Summary” is basically a summary of your settings. As you can see, my resulting file will be 2048×1365 pixels, in sRGB color space, 80% JPEG quality, and the file should be roughly 481 KB once it is exported.
I picked “Desktop” as my destination, but if you have a particular preference for the export location, you can set it from here.
Finally, the recipe has been fully set up. Now all you have to do is pick the image(s) you want to export, then go to File -> Process, or use the CTRL + D (CMD + D on Mac) shortcut to start the export process.
I would recommend to set up similar recipes for all web resolutions you normally use. You can also set up other recipes for printing, etc.
Capture One Image Resizing Process: Exporting as a Variant
The second method of resizing and exporting images in Capture One involves a simple dialog that can be invoked by visiting “File” -> “Export Images” -> “Variants…”. By default, this window does not have a keyboard shortcut, but if you want to create one, you can do so by visiting “Edit Keyboard Shortcuts…” under the “Edit” menu. Another option is to add the Export button to the top menu, which you can perform by invoking “Customize Toolbar…” when right-clicking the top menu area of Capture One.
Once the Export Variants dialog box pops up, it will look like this:
As you can see, the settings are very similar to the ones we have previously seen on the Process Recipes tool. You set up your export destination under “Destination”, a sub-folder if you want to, set up file naming structure and go through different tabs under “Recipe”.
Since the settings are the same, I am not going to go through them again. Once you are done, simply click the “Export Variant” button on the bottom right of the dialog box. The export process will start. If you want to be notified when the export is done, simply check the “Notify When Completed” box under “Options”.
If you have any questions about any of the above, please let me know in the comments section below!
After I do this and resize the photo to the correct dimensions… how can I set it up so that the pics are no more than 200KB in size.
There is a specific program for a client that only allows pics of that size to be uploaded into their system.. I find myself having to export the jpeg and then manually resizing to hit that 200kb size.
I have no clue. Why are you asking me, Micheal?
Thanks for this article. The Process Recipe File tab seems to offer the ability to specify a different destination folder for each process recipe which makes sense to me.
My question is this: I would like to have different Process Recipes which would allow me to export the same image for printing to different paper sizes without recropping the image. Is this possible?
Thank you for sharing this.
In addition to controlling the output size in pixels, is it also possible to set a maximum file size for the exported image?
I want to set the long edge to be 1920 px and the overall file size <= 4Mb.
Does anyone have any ideas on how to do this in Capture One?
I checked with Capture One support, and this is not possible. I will have to reduce the quality of the JPEG to reduce the file size while keeping the long edge length.
Nassim, I have been using your suggested process recipe without question. I’m now seeing others chime in that the long edge, for web viewing, should be maximized for most screen sizes. (desktop, laptop, …) I’m seeing somewhere around 1034 +/-. Thanks for your help.
Nasim, thank you for sharing your process preferences. I have been using 100% jpg quality and ‘restricting’ output based on my ‘as shot’. Of course this has produced very large file sizes that have been modified when uploading to the web. I generally use Apple’s Photos for sharing. Do you have any recommendations specific to Apple Photos? Thanks again. Jon
I miss something in this description, Nasim. Not long ago a friend told me about “JPEGmini”, an app which minimizes files sizes of JPGs in a nearly ridiculous way. Don’t know how they do it, but it works and doesn’t look worse as 2 MB instead of 15 MB should be expected to look. I could not see a difference from the original C1 output to the better compressed one. I don’t use it for album work, but I use it for website pics. Not everybody has a fast broadband connection. And mails also benefit from smaller attachments.
It’s one of my few apps allowed to open the results with “open with”. Recalculating the pictures is very fast
Joachim, I use JPEGmini all the time, including when publishing images at PL. Perhaps you forgot, but I previously published a review of JPEGmini here. In short, it is pretty awesome!
Not sure how it relates to this article though :)
It only relates as a last step in the C1 export process. Instead of sending all exported pictures, maybe from various target folders, to JPEGmini at once they are saved in a minimized size.
You do a Top-Drawer job at this web site. For that I applaud you and hope the very best for you. Your series on resizing introduces two questions from me regarding reducing noise.
1 Should noise reduction always be the first step in post exposure massaging of a image from the camera, resizing or not?
2 – Would you consider at some time in the future making a comparison of noise-reduction applications, in particular the old Nik Dfine , DxO’s version of Dfine, and Topaz’s Denoise?
Take care and Merry Christmas,
Ed, those are some great questions.
1) Yes, noise-reduction should always be run first. Make sure you use non-aggressive noise reduction that doesn’t impact detail. Apply sharpening afterwards.
2) I think that’s a valid request and something I should certainly work on. I still use Nik Dfine quite a bit, but Topaz’s AI Denoise is pretty mind-blowing and something I have been thinking about switching to at some point. Just need to do more testing with it to see how it works in different scenarios. Too bad I missed the Black Friday deal that was 60% off :(
Thanks Nasim for making some space for Capture One. I switched over to C1 a couple of years ago after I noticing that applying brush filters on LR was incredibly sluggish on my computer. That, and the fact that Adobe disabled my own fully purchased products after I tried their subscription (no customer love from on this one). I have been enjoying C1 ever since. My only wish list: a C1 version for iPad.
Fabrice, Capture One should change their pricing, especially their upgrade pricing, since it is getting a bit ridiculous. I don’t like Adobe, but C1 upgrades are so expensive nowadays. Very few new features, and yet each time I have to shell out $100-200 for the features or packs I don’t care about. Also, their DAM needs a lot of work. Too slow and inefficient. Other than that, C1 is a world better for editing compared to Lightroom, especially once you start playing with layers and colors. Adobe tried to copy the color wheels in the latest version of Lightroom, but it is still nowhere close to C1.
I agree C1 is expense to upgrade ever year and the monthly subscription is is more costly than Lightroom.
Did you end up switching over to Capture One from LR? If so, do you plan on doing an article on making the switch and how you’re liking Capture One over LR? I’m like LR as a tool but I *hate* what it does to my computer and how slow it can be.
Elizabeth, partially. I got tired of having to upgrade each time, so I am still running v12 of the software – 2 versions behind. Both C1 and LR have their pros and cons. C1 is better for editing, but takes more time to understand and master, while LR is so much better for file management and cataloguing.
Speed-wise, if you are OK creating sessions for each new shoot, C1 is much faster, especially when dealing with many layers.
I’ve never figured the difference between Output root flder and Output location. And, can you have one photo do two process recipes at the same time?
You cannot process mulitple recipes at the same time, it goes one after another picture. But if you have a multicore processor it almost feels as if they were processed at the same time. And you can choose more than two recipes.
Which you eventually will do without wanting to do so, because the more recipes, the less you see them in the small window.
As for the difference between root folder and location: ask Capture One support to get a rather clueless answer. I figured out: In “Root folder” you can set the output location or another folder. So one tab feeds another tab and makes it rather complicated to keep an overview, but hey, it’s Capture One, supposed the best of all raw-converters this side of the galaxy. No wonder it’s also the best in “very complicated ways to results”…
Geoff, you can run an export with two recipes at the same time. Just select them both from the top, then Process.