Smartphone Video → Editable Character Motion

Free AI Motion Capture From Your Phone: 3D & 2D Animation Guide

Record a performance on an ordinary smartphone, convert it into editable skeletal animation with QuickMagic, retarget the result to a 3D character, or convert the motion for a Reallusion Cartoon Animator G3 Human workflow.

Published April 1, 2025 · Updated July 15, 2026 · QuickMagic Editorial Team

Phone video converted by QuickMagic into 3D motion for 3D and 2D character animation
Direct answer: You can create motion capture with a phone by recording a clear video, uploading the original file to QuickMagic, reviewing the reconstructed body motion, exporting FBX or an available software preset, and retargeting the motion to your character. For Cartoon Animator, convert the output into a compatible Reallusion 3D Motion, load it through the Import 3D Motion panel, choose a projection angle and apply it to a G3 Human timeline.

Current QuickMagic free-plan facts

Maximum clip30 seconds
Maximum upload100 MB
Free exportFBX
ProcessingLow-priority queue
Concurrent jobsUp to 2 mocap videos
Asset storage15 days

Checked against the QuickMagic pricing page on July 15, 2026. Product limits and available formats can change.

Watch the original phone-to-animation tutorial

The original creator video demonstrates a performance recorded on a phone and used for both 3D character animation and a Cartoon Animator 2D character workflow.

Open the original video on YouTube

If the embedded player is blocked by a browser, network, region or local file preview, use the red button. All instructional images below are embedded directly in this file.

How phone-to-motion-capture works

Your phone is the recording device, not the motion-capture computer. QuickMagic receives the uploaded RGB video, estimates the performer's body pose across frames, reconstructs motion in 3D and writes the result as skeletal animation data. The exported animation can then be retargeted to a digital character.

Because the input contains only the views captured by the camera, the reconstruction is most reliable when joints remain visible. Long occlusion, motion blur, cropped feet, low contrast and extreme floor work increase ambiguity.

StageWhat happensWhat you control
RecordingThe phone records ordinary video framesFraming, lighting, sharpness, camera motion and performance
Pose estimationQuickMagic tracks visible body, hand or face features according to the selected workflowSubject selection, capture mode and source quality
3D reconstructionFrame-by-frame pose estimates become a moving skeletal hierarchyModel/preset selection, ground and cleanup options
Export and retargetThe source motion is mapped to a production characterSkeleton preset, frame rate, reference pose, contacts and root motion

1Plan the capture before pressing Record

  • Decide whether you need full-body, upper-body, hand or facial motion.
  • Choose static-camera capture unless the shot specifically requires camera movement.
  • Confirm the destination: Blender, Maya, UE5, Unity, Cartoon Animator or another tool.
  • Choose the target frame rate before recording and exporting.
  • Keep the performance within the active plan's duration and file-size limits.
  • Decide whether the final clip should be in-place or preserve root travel.
Do you need a T-pose? A neutral reference pose can help compare skeleton orientation and retarget poses, but it is not a universal requirement for every QuickMagic workflow. Add a brief neutral stance when your target rig or retarget process benefits from it.

2Record a trackable smartphone video

Camera placement

  • For full-body motion, keep the head and both feet inside the frame throughout the take.
  • Leave margin for wide arm movements, jumps and turns.
  • Place the camera far enough away to reduce perspective distortion.
  • Use a tripod or stable support unless the workflow is configured for a moving camera.

Lighting and exposure

  • Use even front or side lighting that keeps limbs readable.
  • Avoid a bright window directly behind the performer.
  • Prevent the phone from using a slow shutter that produces heavy motion blur.
  • Lock focus and exposure when the phone camera supports it.

Frame rate

Record at 30 FPS for most controlled performances. Use 60 FPS for fast action only when there is enough light to keep frames sharp and the chosen QuickMagic plan and destination support the desired output. A higher frame rate cannot recover hidden joints or blurred silhouettes.

PerformanceSuggested recording approachMain risk
Walk, gesture, dialogue body actingStable 1080p, 30 FPS, full subject visibleCropped feet and slow camera exposure
Dance, kicks, fast turnsBright lighting, 60 FPS when available, extra frame marginMotion blur, self-occlusion and leaving the frame
Kneeling or floor contactWider shot, visible floor, side-front angleHidden limbs and ambiguous contact
Upper-body 2D character actingWaist-up framing with clear hands and torsoHands crossing the body or leaving frame

3Upload and validate the motion in QuickMagic

  1. Transfer the original phone file without re-encoding it through a messaging app.
  2. Sign in to QuickMagic and open Video-to-3D Animation.
  3. Upload the clip and confirm that the correct frame range is present.
  4. Select the subject and capture settings that match the camera and body detail.
  5. Review the preview at normal speed and frame by frame.
  6. Regenerate or refine the source when you see major limb swaps, root jumps or lost contacts.
Avoid messaging-app compression. Some chat and social apps reduce resolution, frame rate and bitrate. Upload the original camera file whenever possible.

4Export the correct motion file

The current Free plan publishes FBX export. Starter and Professional plans list additional presets such as Unreal, Mixamo, BIP, VMD, Unity Anim, C4D, Character Creator/iClone and Roblox.

  1. Choose the skeleton or software preset required by the destination pipeline.
  2. Match the output frame rate to the project.
  3. Preserve an untouched source export.
  4. Name the file clearly, for example Actor_Walk_Phone_Source_30fps.fbx.
  5. Test a short clip before processing a large batch.

3D workflow: phone video to a 3D character

  1. Import the QuickMagic FBX. Create or select the source skeleton in your DCC or game engine.
  2. Prepare the target character. Confirm the target rig, proportions and reference pose.
  3. Map the skeletons. Use the application's retargeting system.
  4. Validate contacts. Check feet, hands, props, root trajectory and floor height.
  5. Polish the target animation. Fix issues introduced by different character proportions.
  6. Export or integrate. Bake only after the editable workflow is verified.
SoftwareTypical workflowPrimary cleanup area
BlenderImport FBX → map bones → retarget to Rigify/custom rigScale, root motion, foot contacts and curve cleanup
MayaImport FBX → characterize with HumanIK or studio retargeterReference pose, floor contact and animation layers
Unreal Engine 5Import source skeleton → IK Rig → IK RetargeterRetarget pose, root motion and target foot sliding
UnityImport FBX → configure Humanoid Avatar → AnimatorAvatar mapping, root transform and foot IK
3ds MaxImport FBX → retarget to CAT/Biped/custom rigRotation flips, key density and contacts

2D workflow: QuickMagic motion to Cartoon Animator

Important compatibility note: Cartoon Animator's Import 3D Motion workflow is designed for compatible Reallusion 3D Motion and G3 Human characters. A generic QuickMagic FBX is not necessarily a one-click direct import. Convert the motion through a suitable Character Creator or iClone pipeline, or use a compatible QuickMagic paid preset where applicable.

Step 1: Convert the QuickMagic output

If you start with FBX, use a compatible Reallusion workflow to convert the human animation into a motion format accepted by Cartoon Animator. Reallusion documents importing FBX or BVH human motion through Character Creator for use in iClone; the exact route depends on the installed product versions and licenses.

Step 2: Use a supported G3 Human character

Reallusion's current Import 3D Motion documentation specifies G3 Human characters. Apply a compatible G3 Human or a Dummy for 3D Motion before loading the converted clip.

Cartoon Animator G3 Human dummy selected from the Content Manager for 3D motion conversion
Reallusion's official G3 Human Dummy for 3D Motion. The Import 3D Motion feature is documented for G3 Human characters.

Step 3: Open Import 3D Motion

  1. Select the G3 Human character.
  2. Open Animation → Import 3D Motion or the corresponding toolbar button.
  3. Load the compatible converted motion.
  4. Preview the linked 3D dummy and 2D character together.
Cartoon Animator Import 3D Motion panel with projection, body and hand settings
The official Import 3D Motion panel includes projection, body, hand, playback and Apply to Timeline controls.

Step 4: Choose the camera projection angle

A 3D motion can rotate freely, but a 2D character is built from a limited set of facing-angle sprites. Choose the projection angle that matches the character design. Reallusion documents front, front-side, side, back-side and back facing concepts.

Cartoon Animator camera projection angle setting for converting 3D motion to a 2D character
The projection setting determines how the 3D motion is represented by a 2D character's available facing angle.

Step 5: Apply and refine the motion

  1. Preview the 3D dummy and 2D character together.
  2. Enable Camera Tracking if the character moves offscreen during preview.
  3. Adjust speed, trim and motion projection.
  4. Use Ground Offset and body posture settings to improve contact.
  5. Click Apply to Timeline and edit the 2D result.
Cartoon Animator workflow from 3D motion import through conversion to a 2D character timeline
Reallusion's official flow: load a 3D motion, configure it in the Import 3D Motion panel, then apply the converted motion to the 2D character timeline.
Cartoon Animator Ground Offset control for correcting a 2D character's contact with the floor
Ground Offset helps correct the character's vertical placement after 3D-to-2D motion conversion.

How to improve phone mocap quality

ProblemRecording fixAnimation fix
Foot slidingKeep feet visible and record a clear floor planeCorrect root speed and target foot contact after retargeting
JitterUse brighter light, stable camera and original video fileApply selective smoothing rather than filtering the full skeleton
Wrong limb after crossing armsChange camera angle or reduce prolonged self-occlusionCorrect the source track or regenerate before export
Knee or elbow popIncrease limb visibility and reduce blurFix retarget pose, pole direction and local keys
2D sprite distortionChoose movement appropriate for the character's available anglesChange projection angle, Flip Body, posture and hand settings

Phone AI mocap vs. traditional motion capture

FactorPhone + QuickMagicProfessional optical system
SetupSingle ordinary video; no markers requiredCalibrated multi-camera volume, markers and specialized workflow
Cost and accessLow entry cost and browser processingHigher equipment, space and operator cost
Occlusion handlingLimited by what the camera sees and learned motion priorsMultiple camera views reduce many line-of-sight failures
Contact precisionOften needs cleanup for feet, hands and floor interactionUsually stronger when the volume and markers are configured correctly
Best fitIndie games, previs, social animation, rapid prototyping and many creator workflowsHigh-end performance capture, demanding VFX and productions requiring controlled precision

Do not use an unsupported universal number such as “within 2–5 cm” to describe all phone captures. Accuracy varies by joint, action, camera, occlusion, output skeleton and evaluation method. Measure the cleanup time and final usefulness for your own pipeline.

Common phone-to-animation problems

ProblemLikely causeRecommended fix
Upload rejectedFile exceeds the active plan's duration or sizeTrim the original file without aggressive recompression and check the current pricing limits.
Motion is soft or unstableLow light, slow shutter, digital stabilization artifacts or compressed sourceRecord in brighter light and upload the original camera file.
Feet disappear from the motionFeet are cropped or hiddenUse wider framing and visible contrast between shoes and floor.
Character scale is wrong in 3DUnit conversion or retarget mismatchCorrect import units and target reference pose before editing animation.
Cartoon Animator cannot load the FBXThe file is not a compatible Reallusion 3D MotionConvert it through a supported Character Creator/iClone pipeline or use an applicable QuickMagic preset.
2D character faces the wrong wayProjection angle does not match the character's spritesChoose a suitable camera projection and use Flip Body for opposite directions.

Frequently asked questions

Can I do motion capture with only a phone?

Yes. The phone records a standard RGB video and QuickMagic processes the uploaded file in the cloud. No marker suit, depth sensor or dedicated capture app is required for the basic video-to-motion workflow.

What are the current free-plan limits?

QuickMagic's current pricing page lists a maximum 30-second mocap clip, 100 MB upload size, FBX export, low-priority processing, two queued mocap videos and 15-day asset storage for the Free plan.

What phone model do I need?

QuickMagic processes standard uploaded video and does not require a specific TrueDepth or depth-camera model for body mocap. Use a phone capable of recording a clear, stable HD video; lighting, framing, blur and visibility matter more than a fixed model list.

Should I record at 30 or 60 FPS?

Use 30 FPS for most controlled actions. Use 60 FPS for fast action when there is enough light to keep the frames sharp and the active plan and destination support the chosen output. Test a short clip before recording a long performance.

Can I import QuickMagic FBX directly into Cartoon Animator?

Not necessarily. Cartoon Animator's Import 3D Motion workflow expects compatible Reallusion motion and supports G3 Human characters. Convert the FBX/BVH through a supported Character Creator or iClone pipeline, or use a suitable QuickMagic software preset when the active plan provides one.

Can phone mocap capture hands and facial motion?

QuickMagic publishes hand and facial options, but usefulness depends on source resolution, framing, visibility and the chosen export workflow. A wide full-body shot contains less facial detail than a dedicated face recording.

Is phone AI mocap as accurate as a studio system?

It is more accessible, but a single camera is more sensitive to occlusion, motion blur, contact ambiguity and depth uncertainty. Judge the result by the cleanup required for your game, animation, previs or content pipeline.

Related QuickMagic guides

Turn a phone video into editable 3D motion

Record a short test, upload the original clip to QuickMagic and validate the motion in your real 3D or 2D character pipeline before processing a full project.

Try QuickMagic AI Motion Capture →

Official references and media sources