# AIXF Media360 — Q&A
**Q: What counts as a “360° image”?**
A: Standard **equirectangular** panorama (2:1 aspect). Examples: 4096×2048 or 8192×4096 JPG.
**Q: Do I have to edit templates?**
A: No core edits. The add-on ships a **template modification** that injects the mount and loader into the XFMG media view.
**Q: Does it support XenAddons Showcase?**
A: Not in this release. If there’s interest, we’ll add a safe auto-mount mode for Showcase item pages.
**Q: Does it read GPano/XMP to detect 360s?**
A: Not yet. Current detection uses aspect ratio (~2:1). If your camera writes GPano EXIF, that will be supported in a future update.
**Q: My image is 4000×2000 but still doesn’t activate.**
A: Increase the tolerance (`data-ratio-tolerance="0.08"`). Also verify the **actual** image URL served to the page isn’t a resized thumbnail.
**Q: Can I turn off auto-rotate?**
A: Yes. Set `data-autorotate="0"` (or use the ACP option if you exposed one).
**Q: Can I change the default zoom?**
A: Yes. Adjust `data-fov`, e.g. `data-fov="80"` (lower numbers = more zoomed in).
**Q: Performance concerns?**
A: The viewer initializes only on media pages and only when a pano is detected. For very large images (8K), initial decode is the heavy part. If needed, we can add lazy-activation and multires tiling in a later update.
**Q: Which licenses are the demo panos under?**
A: Use your own images or CC0/allowed sources (e.g., tonemapped JPGs from HDRI sites). Always verify the license for the specific file you upload.
**Q: How do I report issues?**
A: Include a screenshot of the **Console** (look for `[AIXF]` logs), plus the **Network** status for the CSS/JS files. Share the failing media URL and the image dimensions.