furutahss
Nulume App Icon
iPhone App Support

Nulume Help & Support

Version 1.0 · iOS 17.0+ · iPhone only

Need Help or Found an Issue?

If you have a question, hit a bug, or want to suggest a feature, please get in touch through the online contact form. If a specific clip is not working, telling us the camera, the recording format and the resolution helps a lot.

Requirements & Supported Formats

Operating System iOS 17.0 or later · iPhone only (not supported on iPad)
Input .mov / .mp4 containing H.264, HEVC (8/10-bit) or Apple ProRes
LUTs 3D .cube files, LUT_3D_SIZE between 2 and 64
Network Connection None required (100% offline operation)

Frequently Asked Questions

Q. Which cameras does Nulume work with?

Nulume judges a clip by its container and codec, not by the camera that made it. Anything that is H.264, HEVC or Apple ProRes inside a .mov or .mp4 opens — Apple Log from an iPhone, and S-Log3, C-Log, V-Log or F-Log brought in from another camera. Copy the files onto your iPhone (a card reader into the Files app works well) and open them from Files.

Q. My file will not open. Why?

The most common reasons are:

  • MXF containers (some Canon Cinema EOS recording modes) are not supported.
  • Camera RAW — BRAW, CinemaDNG, Canon RAW, R3D — is not supported.
  • 10-bit 4:2:2 HEVC needs a hardware decoder that not every iPhone has. Nulume decodes one frame at import to check, and tells you rather than failing later.

Nulume always says which of these it hit instead of showing a generic error.

Q. ProRes is greyed out and I cannot select it.

ProRes encoding requires hardware that only some iPhones have. Nulume asks the system which codecs it can actually encode and greys out the rest, so you find out before starting an export rather than after it fails. HEVC 8-bit and 10-bit work on every supported iPhone.

Q. Why is my export a different size from the original?

The export bitrate follows the source rather than a fixed figure. For an ordinary H.264/HEVC camera file, Nulume targets the original's own rate so a 10-bit export does not come out smaller than what went in. For an All-Intra or ProRes original the result is smaller on purpose: those formats compress every frame independently and carry a lot of redundancy that a long-GOP HEVC encode does not need to reproduce the same picture. The estimated size for each format is shown in the export sheet before you commit.

Q. What exactly does the free version limit?

Only the export format. LUT import, preview, LUT strength and all six basic corrections are unlimited and always free, and there is no cap on how many times you can export. The one-time unlock adds 10-bit HEVC and ProRes output — nothing else changes.

Q. I already paid but the paid formats are locked.

Open Settings → Restore purchases inside the app, signed in with the same Apple Account you bought with. The unlock is a one-time non-consumable purchase, so restoring never costs anything.

Q. Where are my imported LUTs stored?

Inside Nulume's own storage on the iPhone. That folder is deliberately marked as excluded from backups, so your LUT library does not travel to iCloud or into an encrypted device backup. Deleting the app removes them, so keep a copy of any .cube files you care about.

Q. What are the two built-in LUTs?

Neutral Apple Log → Rec.709 and S-Log3 → Rec.709 conversions, generated from each format's published transfer function and from CIE chromaticities. They are a technically-derived starting point, not a camera maker's creative LUT — import your own .cube files for a specific look.

Q. Can I trim or cut a clip?

No, and that is deliberate. Nulume does colour only — no timeline, no trimming, no multi-track compositing. If you need to cut, do that in an editor and bring the result here, or grade first and cut afterwards.

Q. Does the export keep my metadata?

Yes. Resolution, frame rate, capture date, location and the audio track all carry over. Audio is copied across without re-encoding, and the video is tagged Rec.709 to match what the LUT produces.

Q. Does Nulume send anything anywhere?

No. There is no networking code, no analytics and no tracking SDKs — everything happens on the device. See the Privacy Policy for details.