Freemium mobile app with a few starter scans; regional storefront pricing varies. US App Store observed 2026-09-05: Premium $5.49/week, $13.49/month, $78.90/year, $209.99 lifetime plus separate scan packs
MagiScan is a mobile 3D-capture and spatial-creation toolkit for iOS, iPadOS and Android. Its current surface combines camera-based object scanning, LiDAR/point-cloud capture where supported, room-plan workflows, single-image-to-3D and text-to-3D generation. Outputs can move into common downstream formats including OBJ, STL, FBX, PLY, USDZ, GLB and GLTF, and first-party material highlights workflows with Unity, Blender, Bambu Lab, Cura, PrusaSlicer, OrcaSlicer, NVIDIA Omniverse and Minecraft. That breadth makes MagiScan more than a simple photogrammetry scanner: it is designed as a mobile entry point into 3D printing, AR, DCC and asset-production workflows. 1
Pricing & access
The app is free to download and gives new users a small number of starter scans before paid usage. Pricing is storefront-specific and should not be generalized globally. The US App Store observed on September 5 lists Premium at $5.49/week, $13.49/month, $78.90/year and $209.99 lifetime, with additional scan packs sold separately. Earlier European storefront observations use different euro prices, which reinforces that regional presentation matters. MagiScan is therefore easy to try, but frequent scanning can become a meaningful subscription or consumable cost depending on workload. 2
Evidence & trust
Current platform sentiment is materially split. The US App Store shows 4.5/5 from roughly 1.4K ratings, while Google Play shows 3.5/5 from roughly 12.2K reviews and more than one million downloads. A single validated G2 review is also positive overall at 4.5/5 but reports slow cloud processing, inconsistent results and retouching needs; because that review is from 2025 and n=1, it receives almost no numeric influence. The two large current store populations are therefore the main external signal, and they argue for a capable product whose experience is not equally consistent across platforms or users. 234
Privacy documentation also needs careful reading. MagiScan's first-party privacy policy says users may request deletion of personal data, subject to lawful retention, and describes commercially reasonable safeguards. The current Google Play Data Safety panel, however, states that data cannot be deleted while also saying data is encrypted in transit. Those statements conflict at face value and may reflect different scopes or implementations rather than a simple factual error. Users who care about account/content deletion should verify the current process with MagiScan rather than assume either disclosure fully describes every data category. 53
Who it's for
MagiScan is best for makers, 3D-printing users, designers, 3D artists, engineers and e-commerce or visualization teams that value a phone-first capture workflow and broad export compatibility. It is especially useful when speed and accessibility matter more than metrology-grade certainty. It is a weaker fit for workflows that require independently validated dimensional accuracy, predictable high-volume processing costs or enterprise-grade privacy documentation before field deployment. 15
Strengths & weaknesses
Strengths
The strongest point is range: one mobile product covers traditional scanning, LiDAR/point clouds, room capture, generative image/text-to-3D, common export formats and several downstream creation/printing ecosystems. The free starting allowance also makes experimentation easy. The main
Weaknesses
consistency and evidence maturity. Android sentiment is substantially weaker than iOS, the only G2 review describes processing/reconstruction friction, and there is no current controlled benchmark showing how accurate MagiScan is across object classes, lighting and capture conditions. The privacy deletion disclosures also need reconciliation. MagiScan is therefore a strong practical mobile 3D toolbox, but professional users should validate both output tolerances and data-handling requirements on their own workflows. 15234