How to fix green tint in video after conversion with Pavtube

A green tint in converted footage is a colour cast that makes skin, skies, clothing and neutral objects appear unnaturally green. It often appears only after transcoding, even when the original file looked correct in a camera, phone or editing application. The underlying issue is usually incorrect colour-profile metadata, a mismatched decode setting or damaged transparency rather than a fault in the recorded image.

Fixing green tint in video after conversion with Pavtube is most effective when you inspect the source first, identify how its colour information is stored and use a controlled export profile. Repeatedly converting an already faulty file can wash out detail or make the cast harder to correct, so the camera original should always remain untouched.

Australian editors also encounter mixed source histories: legacy PAL recordings, NTSC footage from imported cameras and modern HEVC or HDR files from locally sold or imported iPhones. For teams in Sydney, Melbourne and Brisbane, a consistent Rec.709 master and device checks prevent one organisation’s preview from becoming another organisation’s colour-correction problem.

Identify where the green cast begins

Start by comparing three versions: the camera original, the converted file and a freshly exported test from the original. Open all three in the same player or editing application. If the camera original is already green, the problem begins before conversion and may involve white balance, camera settings or an incorrect viewing profile. If only the converted copy is green, focus on metadata and decoder compatibility.

Inspect several frames rather than judging the opening frame alone. A constant green shift suggests a colour-space or matrix mismatch, while green patches, flickering edges or colour that changes during movement may point to an alpha-channel problem. Video scopes can also reveal whether the red and blue channels are being reconstructed correctly.

Test the output in a second player and, if possible, on the device that will display it. Disable hardware-accelerated decoding during one test because some older drivers interpret 10-bit HEVC or HDR streams incorrectly. A browser-based utility such as PicUKIS media tools can provide another format check with a short, non-sensitive clip, although a local editor or player is preferable for confidential material.

Check colour profiles and playback metadata

A colour profile is a set of instructions telling a player how to interpret the red, green and blue values in a file. Common HD footage is tagged as Rec.709, while some software incorrectly identifies standard-definition material as BT.601. When the primaries, transfer curve and matrix coefficients do not match, correctly encoded pixels can still appear green, yellow, pink or washed out.

Also check whether the source is SDR or HDR. Rec.709, BT.2020, HLG, PQ and Dolby Vision use different rules. An HDR file incorrectly labelled as SDR can look unnaturally bright or colour-shifted, while a plain SDR file labelled as HDR may appear dark and greenish. Full-range and limited-range flags are separate from the colour space and should match the intended delivery standard.

Codec and bit-depth settings deserve attention too. A 10-bit HEVC master may decode badly in an older Windows or Mac application even when another player displays it correctly. Confirm that the output uses a compatible profile for its intended audience instead of assuming that every green cast is a camera problem.

Correct the source before exporting

Open the original in an editor that can display the correct camera profile. Log footage from cameras such as Sony, Panasonic or Fujifilm may need its Log-to-Rec.709 transform applied before normal viewing. Applying the wrong transform, applying it twice or using a LUT designed for a different camera can introduce a strong green or magenta cast.

Use white-balance and tint controls only after checking the profile. The vectorscope and waveform can show whether neutral objects remain centred and whether the green channel is disproportionately dominant. A small correction is usually safer than a large change because aggressive tint adjustment can make skin look unnatural while leaving shadows and highlights inconsistent.

Save the corrected version as a new intermediate file with standard broadcast monitoring enabled. Keep the camera original, the corrected master and the conversion output as separate files. This makes it possible to prove whether the green appearance was introduced by editing, conversion or playback.

Configure a clean Pavtube conversion

Use Pavtube HD Video Converter on Windows or Mac to build a straightforward conversion profile. Start with the corrected or approved source, and avoid applying colour filters, transitions or LUTs during the first test. The goal is to isolate the conversion itself rather than combine encoding, editing and grading in one pass.

Keep the original resolution, aspect ratio and frame rate whenever possible. For broad compatibility, H.264 in an MP4 container with a Rec.709 SDR profile is a dependable choice. Where Pavtube provides profile controls, select the appropriate HD or Rec.709 setting and avoid resizing the image unnecessarily. A high bitrate improves detail, but it cannot repair incorrect colour tags.

Export a five-to-ten-second test and compare it with the source at full brightness. Check skin tones, white objects, foliage and any transparent areas. If the test remains green, return to the source metadata before increasing quality settings. Compression artefacts and colour casts are separate problems, so a larger bitrate will not usually solve a mislabelled colour profile.

Resolve alpha and chroma-key issues

A green screen project can develop a green cast when transparency is lost during mixing, editing or export. Check whether the source contains an alpha channel and whether Pavtube is preserving it. Chroma-key footage is often stored as RGB colour plus a separate matte, and an incorrect matte interpretation can reveal the green background across the entire frame.

For layered or screen-based recordings, render the composition against black, white or a neutral colour before export. Unpremultiplied alpha can create bright green or dark halos around edges because colour values have been combined incorrectly. A clean plate or a correctly calculated matte usually fixes this more reliably than adding a general green correction later.

Green spill can remain along hair, glasses and moving objects even when the key itself is sound. Clean those edges with an appropriate spill-suppression tool, then inspect the result on a neutral background. Avoid increasing global saturation while trying to hide a local keying fault.

Test phones and Australian delivery formats

Modern iPhones sold through Australian carriers can record HEVC video, 10-bit colour and HDR, while imported models from the United States or Japan may offer different Dolby Vision or high-frame-rate options. Photos, QuickTime, Adobe Premiere Pro and a generic media player may interpret these files differently. An H.264 Rec.709 SDR copy is often the safest review and social-delivery version.

Older Australian video material commonly used PAL, including 25 and 50-frame-rate variants, whereas imported cameras and archived clips may use NTSC at 29.97 or 30 frames per second. Do not change frame rate while fixing colour. Identify the source standard first, then choose a matching deliverable where timing matters. Contemporary online platforms generally accept either 25 or 30 frames per second when the video is Rec.709 encoded.

Australian agencies, production houses and broadcasters in Sydney and Melbourne regularly exchange material captured with mixed camera packages. Confirm the commissioner’s specification before delivery, especially when the file is headed to SBS, a commercial broadcaster or a festival submission. Cloud transfers can expose incorrect metadata when one side generates review copies automatically, so inspect the uploaded file rather than relying on the local export.

Build a reliable colour-safe workflow

A dependable process combines accurate source interpretation with restrained output settings. The following practices reduce the chance of a green cast returning after an edit, export or platform transcode.

• Preserve the untouched camera original and duplicate it before making any changes.
• Record the source codec, resolution, frame rate, bit depth and colour-profile metadata.
• Use Rec.709 SDR for general HD delivery unless a specified workflow requires another colour space.
• Keep the frame rate and dimensions stable unless the destination has a clear technical requirement.
• Export a short test before processing the complete programme or client batch.
• Review transparent footage against a neutral background and confirm that alpha information is handled correctly.
• Check the approved master in the editing application, a common player and the final delivery platform.

Broader format-specific instructions are available in the DigiSNS how-to guides, while Pavtube provides the conversion and compression stage for Windows and Mac workflows. A stable deliverable is a correctly tagged Rec.709 file that matches the source frame timing and passes colour checks in every environment where it will be viewed.