Skip to article
All posts
By Pravit Gandhi···11 min read

How to grade log footage without DaVinci Resolve

Can you grade log footage without DaVinci Resolve? Yes. Here is the workflow in Premiere, Final Cut, mobile apps and the browser, with the real limits.

You can grade log footage without DaVinci Resolve, and for most delivery work you will not notice the difference. The job splits in two: normalize the log into a viewable space, then build a look on top. Premiere Pro and Final Cut Pro both do the first half automatically now, mobile apps do it with a LUT, and a browser studio like Leumos converts it in the preview, then again when the export renders on its servers. What you give up outside Resolve is nodal precision, tracked secondaries and serious noise reduction. What you get back is a machine that responds when you scrub. If your laptop stalls the moment you enable a grade, that trade is already worth making.

Update scope, September 8–9, 2026: The Leumos workflow, availability, export, and processing disclosures below have been corrected to match the current product, and its built-in scopes and dedicated Skin tone selection and mask are now named. Other-vendor coverage and the wider technical discussion remain the August 2026 material; this is not a new comparative test.

The complaints that bring people here

The searches that land on this page are not about software categories. They are about machines. My laptop cannot run Resolve. A 4K render has been going for twenty hours. Playback is fine until I enable the color page, then it stutters. My new MacBook feels worse than my old one for grading. Those are four different problems and they have different causes.

Start with the published floor, and read the current one rather than a number you saw in a forum thread. Blackmagic ships the minimum system requirements inside the release notes for each version, and they move: recent releases have raised the required macOS version and narrowed which Macs are supported at all. Check the requirements for the exact version you are installing before you conclude anything about your machine. If you are under that line, no preference change saves you, and you will spend more time troubleshooting than grading.

Then check what version you are on. Blackmagic's product page draws the line like this: the free version "works with virtually all 8-bit video formats at up to 60fps in resolutions as high as Ultra HD 3840 x 2160," while Studio at $295 "supports 10-bit video up to 120 frames per second and resolutions beyond 4K," plus the noise reduction and Neural Engine tools. In practice the boundary is softer than that sentence reads: the free version opens plenty of 10-bit intraframe material, ProRes and Blackmagic RAW included, and the wall people actually hit is 10-bit long-GOP H.264 and H.265 from hybrid Sony and Canon bodies, along with anything past UHD or 60fps. If your S-Log3 comes out of a hybrid as XAVC, test your exact files in the free version before you conclude anything from a spec sheet.

The stutter is usually neither of those. Long-GOP H.264 and H.265 require decoding neighbouring frames to build any single frame, so scrubbing is expensive before a single grading operation runs. That is a decode problem, and proxies or optimized media fix it inside Resolve without buying hardware. Try that before you conclude the application is the issue. But if the answer is "my machine is three years old and I have one job to deliver on Friday," the rest of this guide is the faster route.

The two jobs you are actually doing

Normalizing and grading are separate operations, and every tool below is really being judged on how well it separates them.

Normalizing means converting log encoding into a viewable space using a defined transform. Grading means making creative decisions after that. Log footage looks flat because nothing has done the first job yet, which is the whole subject of why your S-Log3 footage looks washed out. A tool that lets you do both but does not let you keep them apart will eventually cost you an evening.

Grading log in Premiere Pro with Lumetri

Premiere's color management does the normalization for you, and this is the part people miss because it changed relatively recently. Adobe's overview names the two controls: a preference called Auto Detect Log Video Color Space and a sequence setting called Auto tone map media. Adobe lists Sony S-Log among the formats detected on import. Under the hood the footage is transformed into a wide gamut working space based on ACEScct with tone mapping, rather than through a LUT you supply.

The practical workflow is short. Import, confirm the clip was detected correctly, and if it was not, set the color space by hand in Interpret Footage. Then grade in Lumetri's Basic Correction and Curves as if the clip were already normalized, because it is. Do not add a conversion LUT in the Creative tab on top of that. Two transforms stacked on each other is the single most common cause of plastic highlights and skin that goes orange as it brightens.

Two caveats worth knowing before you commit a project to it. Detection reads metadata, so log footage that has been transcoded or rewrapped often arrives stripped and defaults to Rec.709, which puts you back to a flat clip and a manual override. And Lumetri gives you one clip at a time with no real mechanism for reconciling forty shots against each other, which is where the hours go on a multicam or event edit. We covered that gap in more depth in our Premiere Lumetri alternative write-up.

Grading log in Final Cut Pro

Final Cut takes the same approach with less ceremony. Apple states that when you import log media, Final Cut Pro detects metadata identifying the log format and automatically applies the appropriate built-in camera LUT. For Sony material there are dedicated entries: Sony S-Log3/S-Gamut3 and Sony S-Log3/S-Gamut3.Cine, each of which applies the appropriate linearization and 709(800%) MLUT tone mapping.

The setting lives in the Info inspector under the Camera LUT pop-up menu, which is also where you override it when the metadata is wrong or missing. Apple supports imported custom camera LUTs in the same menu, so a manufacturer conversion LUT can be slotted in as the input transform rather than dropped on as an effect. That distinction matters: a camera LUT is applied before your color adjustments, a LUT effect after.

Final Cut's color tools are shallower than Resolve's and its scopes are less configurable, but the log handling is solid and the playback performance on Apple Silicon is the reason a lot of people end up here after a bad week with node graphs.

Mobile and consumer apps, and where they run out

LumaFusion is the serious option on iOS and Android. Luma Touch documents importing .cube and .3dl files through either the Library window or the Color and Effects Editor, and there is a known iOS quirk where a LUT appears greyed out because another creative app has claimed the file identifier, fixed by routing the import through the Files app. Once loaded, the LUT applies like any other effect.

That is also the ceiling. A LUT applied as an effect is not color management. You cannot declare an input color space, the app does not know your footage is S-Log3, and there is no transform being computed, only a lookup table being sampled. It works, and for a short piece cut on an iPad it works well. It stops working when you need to offset exposure before the LUT, when you are mixing two camera formats, or when you need scopes to tell you what is actually happening rather than what the phone screen suggests.

The lighter consumer editors are further down the same road. Most have a LUT slot and no scopes at all, which means you are eyeballing a technical transform on a display you have not characterised. For a phone-shot vlog that is fine. For 10-bit S-Log3 you are throwing away most of what you paid the camera for.

Browser tools, and the difference between the two kinds

Browser-based color tools split into two categories that are easy to confuse because they both run in a tab.

The first is the frame grader. Luttie is the clearest example: you upload a still frame, or let it pull one out of an MP4, MOV or WebM, build a grade with curves, color wheels and HSL, then export the result as a .cube at 17 or 33 points, or a .3dl, and apply that file yourself in Resolve, Premiere, Final Cut or CapCut. Its own guidance is sound on log, telling you to apply the technical correction LUT for S-Log3, D-Log M or C-Log3 before building the creative grade on top. If what you want is a portable look you can reuse across projects, that is a good fit and the output lives in your NLE where the rest of your work already is.

The second is the timeline grader, which grades the shots themselves and hands back rendered video rather than a lookup table. Neither category is better in the abstract. They answer different questions: one gives you a look to apply, the other gives you graded footage.

Where we fit, with the disclosure that it is our product: Leumos AI is a browser-based color grading studio with Free, Lite, and Studio plans. Import footage, detect the cuts, choose a shot and a still-image reference, and run a reference match. Review it in motion and refine it with creative and AI-assisted grading controls. You can grade shots individually, copy a grade as a starting point for another shot, and export the graded timeline. Reference match uses a still image for the selected shot. Match shots uses a graded shot to match the rest of the edit; review and refine the sequence before export.

For shot review, use the built-in waveform and vectorscope, then use the dedicated Skin tone control to automatically select skin, inspect and refine its mask, and adjust it separately from the overall grade.

For log footage, select the named input transform for the source encoding and gamut before evaluating the look. The Studio includes Sony S-Log3/S-Gamut3 and S-Log3/S-Gamut3.Cine options; they are different input choices. Do not apply a log transform again if it is already baked into your video. The log reference tool explains the effect of decoding with the wrong log curve. This is input preparation, not evidence that reference matching will reproduce every part of a still's look.

The browser interface still uses your device for preview and interaction. The preview plays from the file on your device, but scene detection and reference matching send material to the server. Export uploads original footage for server rendering. Every plan, Free included, also keeps a cloud copy of your footage in an account pool (Free 1 GB, Lite 4 GB, Studio 20 GB) unless you opt out; read the privacy policy for the transfer details, including when a reference match needs source footage. A connection and time for uploads and processing are part of the workflow; this article does not establish a speed advantage on your laptop.

Leumos is live. Use your editing software for the broader edit and audio, then check the current workflow FAQ and plan-specific resolution, bit depth, and ProRes 422 HQ availability. Start with the Free plan and evaluate the result on a representative shot before committing the rest of an edit.

If the scene-cut part is the interesting bit, we explained the mechanics separately in how AI scene detection works. For the wider category these browser tools sit in, see browser color grading tools compared by category.

A workflow that survives a slow machine

Assume a four year old laptop, 10-bit S-Log3 from a Sony body, and a twelve minute edit due tomorrow.

  1. Cut with proxies. Whatever editor you are in, generate low resolution proxies before you touch color. Most performance complaints are decode complaints and this removes them.
  2. Lock picture before you grade anything. Every color decision made against a cut that is still moving gets redone.
  3. Normalize once, in one place. Let Premiere's color management or Final Cut's camera LUT do it, or apply a manufacturer conversion LUT as an input transform. Then never touch it again.
  4. Grade the look on top, on the timeline or in a browser tool, whichever your machine tolerates.
  5. Switch off proxy playback before you export. This is the step people skip, and it is how a soft master reaches a client. Then export at full resolution from the tool that has the fewest transforms stacked in it, and check the result in the player your client will actually use.

That order is boring and it is the reason people who deliver on time deliver on time. If you are still weighing whether to leave Resolve entirely, our DaVinci Resolve color grading alternative guide and the browser-based options go tool by tool in a way this workflow guide deliberately does not.

Frequently asked questions

Can I grade S-Log3 in Premiere Pro without a LUT?

Yes. Turn on Auto Detect Log Video Color Space and enable Auto tone map media on the sequence, and Premiere transforms the footage into its wide gamut working space without any LUT file. If a clip is not detected, override its color space in Interpret Footage rather than adding a conversion LUT on top.

Does Final Cut Pro handle S-Log3 properly?

Yes. Apple ships camera LUTs for both Sony S-Log3/S-Gamut3 and S-Log3/S-Gamut3.Cine, applied automatically from the file's metadata and adjustable in the Info inspector. They apply linearization plus 709(800%) MLUT tone mapping, which is a real input transform rather than a filter dropped on the clip.

Is the free version of DaVinci Resolve enough for log footage?

Sometimes. Blackmagic's stated split is 8-bit formats up to 60fps and UHD for free, with 10-bit and beyond-4K listed under Studio, but the free version does open many 10-bit intraframe formats such as ProRes and Blackmagic RAW. The consistent trouble spots are 10-bit long-GOP H.264/H.265 from hybrid cameras and anything past UHD or 60fps. Test your exact camera files before building a project around either answer.

What is the fastest way to grade log on a laptop that cannot run Resolve?

Cut with proxies in whatever editor already runs, let that editor's color management normalize the log, and move the creative grade to a browser tool that runs the heavy steps, reference matching and the final render, on its own servers, while the preview still uses your computer's graphics. The decisive question is which application leaves you enough headroom to actually make decisions, whatever its power on paper.

Sources

Related: How to color grade video walks the seven steps in order, and color correction vs color grading explains why normalising and correcting come before any look.