Find answers to the most common questions about ExploreXR — the WordPress plugin for interactive 3D models and augmented reality by ExpoXR. Questions are grouped by topic: general use, the free version, Premium features, AR and WebXR, performance, licensing, GDPR, and support.
ExploreXR is a WordPress plugin by ExpoXR that enables interactive 3D model viewers, browser-based augmented reality (WebAR), WebXR experiences, and modular viewer enhancements. It integrates with Elementor, Gutenberg, and standard WordPress shortcodes — no coding required for standard deployment.
ExploreXR adds interactive 3D model viewers to WordPress pages. Visitors rotate, zoom, and inspect 3D models directly in the browser. With Premium add-ons, models can support augmented reality, animation playback, material switching, annotations, WooCommerce integration, and more.
Yes. ExploreXR is fully no-code for standard deployment. Upload a 3D model, configure settings in the WordPress admin, and embed using a shortcode or Elementor widget — no developer involvement required.
No. ExploreXR uses local dependencies only. No external CDN, no third-party service subscription, no external hosting required. Models are stored in your WordPress uploads directory at `/wp-content/uploads/explorexr_models/`.
ExploreXR supports GLB, GLTF, and USDZ files — ideal for modern 3D and AR experiences.
No. ExploreXR is completely no-code. Upload a model, configure your options, and insert it via shortcode or Elementor.
Simply copy the generated shortcode and paste it into any post or page:
Replace `1` with the actual model ID.
No. ExploreXR includes:
This ensures smooth performance even with large models.
Models are securely stored in:/wp-content/uploads/explorexr_models/
This follows WordPress media storage standards.
Yes — ExploreXR collects zero personal data, uses local dependencies, and follows WordPress security guidelines.
These features are available in the Premium, including:
The free version supports static models only.
ExploreXR performs a clean uninstall, preserving your uploaded models and settings while removing plugin data safely.
The plugin includes:
Security is a top priority.
You can find step-by-step tutorials and real use cases on YouTube. A great starting point is the interactive 3D hero tutorial, which shows how to build a complete 3D section in WordPress within minutes using ExploreXR. Watch tutorial: https://youtu.be/RTTJ6lX6uXw
ExploreXR uses three paid tiers:
Each tier is available in three license categories:
All paid plans include unlimited 3D models.
ExploreXR is the product. ExpoXR is the name behind it.
It gives teams a production-ready alternative to custom 3D builds, disconnected viewers, and image-only product presentation by turning WordPress into a platform for structured XR publishing.
ExploreXR is built for businesses, agencies, technical teams, educators, and content owners who need 3D and AR to function inside real website workflows.
ExploreXR is ExpoXR’s flagship product: a WordPress XR platform for publishing interactive 3D models, mobile AR experiences, and modular advanced viewer capabilities through a structured core-plus-add-ons architecture.
Yes. You can upload and manage unlimited models in both the free and premium versions.
Yes. The licensing structure is designed to support that kind of growth path.
Paid licenses include a 90-day grace period before premium capability is deactivated. This allows time to renew without immediate disruption.
The configuration is preserved. If the add-on is reactivated later, the saved settings return.
Yes. Pro and Plus customers can adjust their active add-ons within the limit of their plan.
Yes. Unlimited 3D models are included on every paid plan.
Each plan is available as Personal for 1 website, Business for 5 websites, and Agency for 25 websites.
Pro includes 2 add-ons, Plus includes 4 add-ons, and Ultra includes all add-ons.
There are three paid plans: Pro, Plus, and Ultra.
Yes. The platform includes bundled support for Draco and Basis Universal workflows.
There is no ExploreXR-imposed model count limit, but file handling still depends on hosting constraints and good asset optimization practices.
USDZ is required for native iOS AR workflows.
`.glb` is usually the strongest choice because it is compact, self-contained, and easier to manage inside WordPress.
ExploreXR supports `.glb`, `.gltf`, and `.usdz`. Poster images use `.jpg` `.webp` and `.png`.
AR, Annotations, Expert Camera Mode, Environment And Lighting, and Animations are common starting points.
AR, WooCommerce Integration, Material Variants, and Annotations are common starting points.
No. It is included free with every ExploreXR installation.
No. Add-ons require the ExploreXR core platform.
Yes. Secure delivery is required for proper AR behavior.
The AR viewing experience itself requires a supported mobile device. Desktop can still support bridge workflows such as QR handoff where configured.
Yes, with the correct supported asset and browser conditions. iOS relies on USDZ for native AR behavior.
Yes. The AR add-on supports mobile AR workflows on supported devices and browsers.
There are 13 add-ons in the current ecosystem, including the always-free Debug Toolkit.
Yes, depending on the website count allowed by the selected license category.
Yes. WooCommerce integration is handled through the WooCommerce add-on.
Yes.
Yes.
Yes.
Yes.
The difference is the full platform around the viewer: modular architecture, licensing, diagnostics, support workflows, large-model handling, and a long-term product roadmap.
Yes. That should still be planned with asset size and page performance in mind.
Yes. Loading behavior can be configured for direct display, poster-first interaction, or lazy loading depending on the asset and page context.
The platform is built to keep asset loading scoped to relevant pages wherever possible, helping reduce unnecessary overhead on unrelated pages.
Use the support page at https://expoxr.com/explorexr/support/
Include version details, active add-ons, a clear reproduction path, screenshots if relevant, and any Debug Toolkit findings.
Start with the documentation, then use the Debug Toolkit to inspect the environment and configuration.
You need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from Turnstile to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More Information
