Shooting Anamorphic on Android: How to Configure PrimeCam for Proper Desqueeze

Reliable Android smartphone video anamorphic lens support requires treating geometry as a post-production operation rather than an automatic in-camera function. Because the Android operating system does not write standardized anamorphic pixel aspect ratio metadata to recorded video containers, achieving true widescreen cinema framing requires understanding how your optical adapter compresses the image, how your capture tools monitor exposure and focus, and how to scale that raster precisely in non-linear editing software.

For independent cinematographers and videographers, anamorphic adapters offer distinctive widescreen flares, oval bokeh, and an expanded horizontal field of view without cropping away vertical sensor resolution. However, mounting cylindrical glass to a mobile device introduces unique optical and computational challenges. This guide explains how to rig, expose, monitor, and desqueeze anamorphic footage using PrimeCam on supported Android hardware, ensuring your footage transitions cleanly to an editorial timeline in Apple Final Cut Pro.

Why Android Smartphone Video Anamorphic Lens Support Is Mostly a Workflow Problem

Anamorphic cinematography relies on asymmetrical optical elements. While a standard spherical lens projects a circular image that maps proportionally onto a camera sensor, an anamorphic front element or adapter contains cylindrical glass. This cylinder compresses the incoming horizontal axis of light by a specific optical factor—commonly 1.33x, 1.55x, or 1.8x—while leaving the vertical axis unaltered. The resulting picture squeezes a wide horizontal field of view into a conventional 16:9 rectangular sensor raster. To display natural proportions, that recorded image must be stretched back out during editorial playback.

The core bottleneck facing mobile filmmakers is that Android does not offer system-level anamorphic lens flags. When you capture a video stream through the Android Camera2 API, the operating system encapsulates frames in standard rectangular pixel ratios (1:1 square pixels). No native operating system flag exists to instruct third-party operating systems, social platforms, or desktop video suites that a given clip requires a 1.33x or 1.8x horizontal expansion.

To establish a resilient mobile workflow, consider the three distinct environments where anamorphic desqueeze can occur:

• The Live Monitor Preview: View-only software scaling inside the camera app that stretches the camera preview on screen so the camera operator can evaluate composition without squinting at distorted faces and distorted horizon lines.
• Container-Level Metadata: Video container headers (such as QuickTime atom or MP4 track headers) that attempt to declare non-square pixel aspect ratios. While standardized in broadcast files, desktop NLEs frequently ignore or misinterpret non-square pixel flags generated by mobile media frameworks.
• The Non-Linear Editor (Post-Production): Manual or preset-based transform scaling applied directly to the clip or sequence inside your editing software. This remains the only universally reliable method for professional delivery.

The operational rule for Android smartphone video anamorphic lens support is clear: treat the phone purely as a high-fidelity capture device and treat your desktop editor as the definitive environment where optical geometry is restored. The squeeze factor is strictly an optical property of the glass mounted in front of the lens module—it is not an intrinsic property of the mobile device or operating system—and it must be documented systematically by the camera operator on set.

What an Anamorphic Adapter Actually Does to an Android Camera

Attaching an Android cinema lens adapter to a smartphone transforms the optical physics of the native lens stack. Because smartphone camera sensors rely on small native focal lengths (often between 6mm and 7mm for primary wide sensors) with wide maximum apertures, placing auxiliary glass directly in the optical path introduces immediate geometric and visual consequences.

Framing, Distortion, and Resolution

When looking at an uncorrected anamorphic feed, circles project as tall ovals, and human subjects appear unnaturally narrow. Beyond this compositional distortion, desqueezing reshapes your final pixel distribution. Anamorphic adapters do not add physical sensels to your device; instead, they optically pack wider scene information across the existing sensor width. When you desqueeze mobile footage in post-production by stretching horizontal pixels, you dilute effective horizontal pixel density relative to the vertical axis. For example, stretching a 3840×2160 UHD capture horizontally by 1.33x creates an uncropped canvas equivalent to approximately 5107×2160. If you scale that raster into a standardized 2.39:1 delivery timeline (3840×1608), you discard top and bottom headroom while interpolating horizontal detail.

Focus Shifts and Optical Softness

Anamorphic adapters add multiple glass elements that alter the native lens's minimum focus distance. A smartphone camera that normally resolves subjects at close range may suddenly struggle to achieve sharp focus inside a meter when adapted. Furthermore, cylindrical glass induces astigmatism and field curvature, which can cause edge-to-edge sharpness to drop. While the center of the frame might retain high modulation transfer function (MTF) sharpness, the extreme edges can exhibit chromatic aberration, astigmatism, and barrel distortion.

Optical Character: Streaks and Bokeh

Filmmakers embrace anamorphic mobile filmmaking primarily for optical character. Point light sources hitting the cylindrical elements generate horizontal streaks, while out-of-focus background highlights take on characteristic elliptical geometries. These optical properties cannot be accurately replicated using post-production plugins; they are rendered physically by the glass before the sensor ever digitizes the light.

Before taking an adapter into the field, execute this three-point pre-shoot inspection:

1. Shoot an optical grid or chart: Align your device perpendicular to a printed high-contrast grid to identify edge curvature, center sharpness falloff, and adapter tilt.
2. Shoot a portrait subject: Frame a face at standard dialogue distance to examine how skin textures and fine facial hair render under optical compression and subsequent horizontal interpolation.
3. Shoot an isolated specular highlight: Aim a small LED flashlight directly down the lens axis in a darkened space to inspect the symmetry, color, and internal scattering of optical flares.

Mounting an Android Cinema Lens Adapter Without Ruining Your Rig

Mobile anamorphic adapters cannot simply be clipped haphazardly over a smartphone casing. A misaligned adapter degrades optical performance and produces uncorrectable optical flaws.

Mounting solutions fall into three main mechanical categories:

• Universal Clip-On Brackets: Inexpensive spring-loaded clamps. These are unstable, slip under minor bumps, flex under their own weight, and inevitably drift off-axis during operation. They should be avoided for cinematic work.
• Dedicated Lens-Mount Phone Cases: Cases with integrated bayonet or 17mm/37mm threaded rings. These provide consistent positioning directly over the sensor module, but plastic cases can flex under ambient heat or heavy glass.
• Machined Aluminum Cages: Rigid metal enclosures featuring adjustable mounting plates and standardized 1/4"-20 and cold-shoe threads. Cages allow you to mechanically secure the adapter while distributing the mass across a stabilized base.

Because an anamorphic adapter adds front-heavy glass far past the smartphone's center of gravity, handheld micro-jitters become visibly magnified. When rigging your phone, ensure proper weight distribution by attaching side handles, an external baseplate, or a lightweight rail system. When pairing adapters with multiple lenses, reference the Android cinema camera lens rail guide to understand how physical lens brackets isolate torque from the smartphone's camera assembly.

Alignment is critical: the adapter's optical squeeze axis must sit precisely parallel to the sensor’s horizontal plane. If the adapter is rotated by even two or three degrees, the horizontal squeeze is imposed at a diagonal angle. When you attempt to apply a standard horizontal desqueeze in an editor, vertical lines will tilt, skewing facial geometry and architecture in a manner that cannot be resolved without complex warping transforms.

Be aware of optical vignetting. Smartphone ultrawide lenses (such as 13mm-equivalent modules) have extremely wide acceptance angles that capture the physical interior barrel of an anamorphic adapter, resulting in black rounded corners. Most 1.33x and 1.55x mobile adapters are engineered specifically for primary wide lenses (roughly 24mm to 28mm equivalent focal lengths) and will vignette severely if placed over wider glass.

Mounting Checkpoint	Acceptable Operational Tolerance	Failure Mode If Ignored
Rotational Axis	0.0° deviation (checked against grid)	Skewed geometric distortion; vertical architecture tilts when desqueezed.
Sensor Coverage	Zero mechanical vignetting in corners	Dark clip borders requiring destructive post-production cropping.
Clearance & Gap	Glass surfaces parallel, < 1mm gap	Severe internal ghosting, contrast reduction, and loss of edge focus.
Mechanical Rigging	Metal cage with rigid lens plate	Mount flex under thermal expansion or movement, causing optical drift.

Configuring PrimeCam for Anamorphic Capture

Capturing anamorphic video requires an app that treats your video feed with technical fidelity. PrimeCam writes HEVC Main 10 in a .mov file with the hvc1 sample entry and a full Rec. 2020 HLG colour tag, which Final Cut Pro reads natively. This ensures that the wide tonal range and high contrast produced by anamorphic flares and specular pinpoints remain intact throughout production without clipping or banding.

Regarding encoding, PrimeCam does not record ProRes. It writes HEVC Main 10, which Final Cut Pro opens natively without transcoding. Furthermore, PrimeCam records HLG, not LOG. HLG is a display-referred curve that carries its own grade; there is no LOG profile. The Hybrid Log-Gamma transfer function—standardized in ITU-R Recommendation BT.2100—provides broad dynamic range handling across highlights and deep shadows, which is valuable for preserving high-intensity anamorphic lens flares.

Regarding hardware compatibility, the developer reports testing on Pixel 11, Pixel 10 Pro and Pixel 10, plus a Samsung phone on 15 September 2026 whose model has not been recorded. Earlier documented field testing also covers Pixel 10 Pro XL and Pixel 6a. These reports do not establish support for all Samsung phones or every recording mode; capabilities vary by device. Developer testing on 15 September 2026 found that Pixel 9a does not support 10-bit recording in PrimeCam; it is not a supported device for the current 10-bit HLG recording mode. It requires Android 13 or later and a camera that can record 4K in 10-bit HLG.

PrimeCam 0.1.0 is available on the Google Play production track. It is still an early release, not a guarantee of readiness for irreplaceable footage. PrimeCam does not request Android INTERNET permission. Recording and subject detection run locally, with no PrimeCam account, analytics SDK or cloud sync. Billing-enabled test builds communicate with Google Play for product details, purchases and restoration; Google Play uses its own network connection. No footage is sent through billing.

To configure PrimeCam for anamorphic production, follow this explicit order of operations:

1. Container and Color Baseline: Confirm that the recording format is set to 10-bit HLG. This establishes an industry-standard Rec. 2020 wide-gamut baseline wrapped in a standardized QuickTime `.mov` container.
2. Resolution Selection: Choose 3840×2160 recording where device hardware supports it. Anamorphic desqueeze stretches pixels horizontally, meaning higher native sensor acquisition delivers critical extra data for clean interpolation in post.
3. Frame Rate Configuration: Select your target frame rate (e.g., 24 fps). PrimeCam targets 24 fps, and says so rather than assuming it. A take can come in marginally under nominal — auto exposure opening the shutter to the whole frame period leaves the sensor no time to read one out — so the app reports the rate it actually achieved in three places: the strip switches to the measured rate in warning colour while the take is rolling, the take card reads "23.92 fps measured, not 24.000", and the JSON sidecar carries measuredFps beside the requested fps. In that sidecar metadata, measuredFps is null when the take held close to its nominal rate and records a specific figure when it drifted, so an editor conforming a timeline can tell the two cases apart.
4. Monitoring Activation: Turn on on-screen analytical instruments: the waveform monitor, false colour overlays, and focus peaking.
5. Exposure and Focus Locks: Lock your exposure parameters (ISO and shutter speed) and manual focus distance. Adding an anamorphic adapter changes incoming light transmission and contrast boundaries, which can cause continuous auto-exposure and autofocus algorithms to hunt distractingly.

For editors planning downstream color passes, read our in-depth breakdown on how to edit 10-bit HLG video in Final Cut Pro to guarantee your project color space perfectly mirrors your capture container.

Monitoring a Squeezed Image: Waveform, False Colour and Focus Peaking

Operating a camera while monitoring an optically squeezed preview requires strict reliance on objective metering instruments. Because the live viewfinder compresses faces and landscape elements along the horizontal plane, intuitive visual assessments of sharpness and highlight roll-off can be deceiving.

Fortunately, luminance is an optical absolute unaffected by horizontal compression. PrimeCam's exposure evaluation tools—the live waveform monitor and false colour display—evaluate the actual sensor raster prior to any monitoring scaling. If a specular flare creates a peak that hits 100% IRE, the waveform alerts you immediately, regardless of how narrow or wide that flare appears visually. Learn how to configure these exposure ranges via our guide to false colour exposure mapping and our breakdown of the in-app waveform monitor.

Conversely, focus peaking must be treated with technical caution on an optically squeezed preview. Focus peaking algorithms evaluate high-frequency contrast transitions between neighboring pixels. Because an anamorphic adapter compresses the horizontal axis optically, fine horizontal details are crowded closer together on the sensor. This high pixel density can cause the peaking engine to highlight edges intensely, making scenes look tack-sharp on a small phone screen even when the focus plane is slightly off. Do not rely exclusively on peaking lines for critical shots; punch in with a focus magnifier to confirm focus manually on your subject's eyes before rolling.

When subject-detection autofocus is engaged, PrimeCam focuses on the subject's nearer eye, and falls back to the head and then the body when it cannot resolve one — the ladder professional stills and cinema bodies use, and which was historically confined to them. It names the rung it is actually on: EYE, FACE, BODY, or NO SUBJECT. Faces and their eye positions come from the Pixel's own image signal processor; bodies, animal heads and eyes, and faces turned to profile come from models bundled in the app. Nothing leaves the device. Subject detection runs on models bundled inside the app, not on a server, and names the rung it is holding — EYE, FACE, BODY, or NO SUBJECT.

Be aware that an anamorphic adapter's optical aberrations (such as peripheral astigmatism or chromatic fringing) can reduce edge contrast. If an actor moves toward the far edges of the frame, the tracking system may transition down the ladder from EYE to FACE or BODY more readily than it would with native spherical optics. Keep critical tracking subjects framed closer to the optical sweet spot in the center two-thirds of the sensor when shooting through auxiliary anamorphic glass.

Desqueezing Anamorphic Video in Final Cut Pro and Non-Linear Editors

Once you transfer your recorded takes from your Android device to your editing workstation, you must perform the geometric desqueeze. Because the captured media uses standard 1:1 square pixel metadata, desktop video software displays the squeezed 16:9 file by default.

In Apple Final Cut Pro, restoring proper proportions can be handled either through clip-level anamorphic overrides or spatial transform adjustments, as documented in the Final Cut Pro anamorphic clip properties guide. The two primary methods are:

Method 1: Anamorphic Override Setting

In the Final Cut Pro browser, select your imported clips, open the Video Inspector or Info Inspector, switch the metadata view to Settings, and locate the Anamorphic Override property. If your optical adapter squeezed footage by 1.33x, selecting the 1.33x preset automatically flags the media for widescreen playback. For 1.55x or 1.8x mobile glass where no preset matches the exact factor, use the transform method below.

Method 2: Spatial Transform Scaling (Universal Method)

The manual transform method gives you exact mathematical control over any optical compression ratio:

1. Create a custom project sequence matched to your target widescreen aspect ratio. For a standard 2.39:1 scope master derived from a 3840×2160 UHD capture using a 1.33x lens, set project dimensions to 3840×1608 (or 5107×2160 for an unscaled canvas).
2. Place the squeezed clip on the timeline.
3. In the Video Inspector, locate the Transform section and unconstrain the Scale parameters (or adjust Scale X independently).
4. Set Scale X to match your optical squeeze factor: for a 1.33x adapter, set Scale X to many (keeping Scale Y at many); for a 1.55x adapter, set Scale X to many (keeping Scale Y at many); for a 1.80x adapter, set Scale X to many (keeping Scale Y at many).
5. Set the Spatial Conform property to None so that Final Cut Pro does not fit or fill the frame automatically before applying your transform values.

Because PrimeCam writes HEVC Main 10 in a .mov file with the hvc1 sample entry and a full Rec. 2020 HLG colour tag, which Final Cut Pro reads natively, your timeline retains full wide-gamut HDR color accuracy throughout every geometric scaling step.

Frequently Asked Questions

Does Android support native anamorphic video metadata?

No. Android does not write standardized anamorphic pixel aspect ratio metadata flags into captured video containers. Android camera frameworks record frames using 1:1 square pixel geometry, meaning all optical desqueezing must be calculated and applied either via monitoring tools during shooting or inside non-linear editing software during post-production.

Why PrimeCam Does Not Record ProRes for Anamorphic Capture

PrimeCam does not record ProRes. It writes HEVC Main 10, which Final Cut Pro opens natively without transcoding. This workflow provides 10-bit color depth and Rec. 2020 HLG dynamic range while keeping file sizes significantly smaller and easier to manage than uncompressed broadcast codecs.

Why PrimeCam Records HLG Instead of a LOG Profile

PrimeCam records HLG, not LOG. HLG is a display-referred curve that carries its own grade; there is no LOG profile. The 10-bit HLG curve protects specular anamorphic highlights and shadow information cleanly across modern wide-gamut displays.

What happens if my anamorphic lens adapter is slightly rotated off-axis?

If an anamorphic adapter is rotated even a degree or two away from horizontal alignment, the compression occurs along a tilted diagonal axis. When you stretch the horizontal axis during editing, the image will display trapezoidal skewing where vertical lines lean sideways. This optical alignment error cannot be corrected with simple horizontal scaling and requires complex post-production warping.

Which Android phones are confirmed to work with PrimeCam?

The developer reports testing on Pixel 11, Pixel 10 Pro and Pixel 10, plus a Samsung phone on 15 September 2026 whose model has not been recorded. Earlier documented field testing also covers Pixel 10 Pro XL and Pixel 6a. These reports do not establish support for all Samsung phones or every recording mode; capabilities vary by device. Developer testing on 15 September 2026 found that Pixel 9a does not support 10-bit recording in PrimeCam; it is not a supported device for the current 10-bit HLG recording mode. It requires Android 13 or later and a camera that can record 4K in 10-bit HLG.

Does PrimeCam send my footage or diagnostic data to a cloud server?

PrimeCam does not request Android INTERNET permission. Recording and subject detection run locally, with no PrimeCam account, analytics SDK or cloud sync. Billing-enabled test builds communicate with Google Play for product details, purchases and restoration; Google Play uses its own network connection. No footage is sent through billing.

What is the current release status and reliability of PrimeCam 0.1.0?

PrimeCam 0.1.0 is available on the Google Play production track. It is still an early release, not a guarantee of readiness for irreplaceable footage. A take is written as a spanned clip: numbered parts of a few seconds each, each one finished as it is written. If the app stops unexpectedly the last few seconds are lost rather than the whole take, and the parts carry the take's name and import as one clip. That is a floor on what a crash costs, not a promise that nothing is lost: PrimeCam 0.1.0 is an early build and nothing irreplaceable should be shot on it yet.