Help & Support

UFO Tracker is a community-driven platform for reporting and tracking UFO/UAP sightings. Browse a real-time map of reports from sky watchers around the world, submit your own sightings with photos and video, and verify what others have seen. Available on the web at ufotracker.xyz and on iOS.

Click "Sign in" in the header. You can sign in with Apple, Google, or an email magic link. There are no passwords — you'll either authenticate via your existing account or click a link sent to your email.

No — you can view the map and feed without signing in. An account is required to submit sightings, comment, verify, like, and follow other users.

Most things work the same: browse the feed and map, view sightings, submit reports, verify/like/comment, follow users. The iOS app adds device push notifications and uses your phone's camera natively. Everything else is at parity.

Red dots are sightings from the last 24 hours. Orange is the last week. Yellow is the last month. Gray dots are older. The legend is in the top-left of the map.

Click any dot to open a popup with the shape, location, and a "View sighting →" link. Clusters (numbered blue circles) zoom in when clicked.

Use the geolocate control on the right side of the map. Your browser will ask for location permission.

The map cache refreshes about every 5 minutes. If your sighting still doesn't appear, double-check it saved successfully and that visibility is set to Public on the sighting detail page.

The 60 most recent public sightings, sorted by date sighted (newest first). Use the date and source filter pills at the top to narrow down.

Click any chip in the Source row: All sources, Community (user-submitted only), AARO (U.S. Department of Defense), GEIPAN (France's CNES), Blue Book (NICAP's Project Blue Book mirror), or DHS / CBP.

UFO Tracker ships with a curated archive of real, public-domain UAP cases from AARO, GEIPAN, DHS/CBP, and NICAP's Project Blue Book mirror. Each is clearly labeled with its source agency on the sighting detail page and links back to the original release when a reference URL exists.

Required: at least one photo or video, object shape, a description, and a location. Recommended additions: date/time seen, color, movement pattern, count, witnesses, duration, camera type. The more detail, the more useful for the community.

UFO Tracker is a visual archive — every report needs supporting media so others can see what you saw. If you witnessed something but didn't capture it, we recommend writing it up elsewhere.

Click "📷 Camera" to open your device camera (mobile) or "🖼 Photo / video" to pick from your library. You can attach up to 5 items per sighting. Photos are limited to 8 MB and auto-resized for upload. Videos can be up to 200 MB.

No. The web client extracts the GPS to auto-fill the sighting location, then strips all EXIF (including GPS, camera info, and timestamps) by re-encoding the image through canvas before upload. Only the coordinates you confirm in the form are sent to our servers.

Three options: GPS auto-fills from the first photo's EXIF if present, click "📍 Use my current location" to use your browser geolocation, or click/drag the pin on the map.

Yes — both fields support multi-select. Click each chip to toggle on/off. Useful when an object changed shape or moved in multiple ways.

Optional category for what device captured the media: phone, DSLR, FLIR/thermal, night vision, drone, dashcam, or other. Helps viewers judge image quality and context (e.g. thermal-IR footage versus a phone camera).

Optional URL to an external source — news article, official video, social post, etc. It becomes a tappable link on the sighting detail page.

Open any sighting and click the Verify button. This signals to others that the sighting looks legitimate. Click again to un-verify.

Verify is your assessment that the sighting appears credible. Like is for sightings you find interesting or want to bookmark. Both counts are public.

Sign in, scroll to the comment section on any sighting, type your comment, and click Post. Comments are public and tied to your account. You can delete your own comments at any time.

Open the sighting and click the ⋯ menu in the top-right (only visible on sightings you own) → Edit. All fields can be changed and you can add or remove media.

Open the sighting → ⋯ menu → Delete (only visible on sightings you own). Deletion is permanent and removes all uploaded media from storage.

Click your avatar in the header → Edit profile. You can update display name, bio (250 chars), location, and avatar. Username is fixed once chosen.

Usernames are unique identifiers used in profile URLs (e.g. /u/your-username). Allowing changes would break existing links and references.

Click your avatar in the header → Sign out.

Avatar dropdown → Danger zone → type your username to confirm. This permanently removes your profile, sightings, uploaded media, comments, likes, verifications, follows, and auth record. The same flow exists in the iOS app at Profile → Privacy & Security → Danger Zone.

Open their profile (click their name or avatar anywhere in the app) and click Follow. Their new sightings appear at the top of your feed.

Click your avatar → My profile. Follower and following lists are coming to the web soon — currently only visible in the iOS app.

Click the 🔔 icon in the header to open your inbox. The badge shows your unread count. The inbox holds notifications from the iOS app too — both platforms share the same notification log.

Avatar dropdown → Notifications → Enable notifications. Your browser will ask for permission, then push alerts arrive even when this tab isn't open. On iOS Safari, add the site to your Home Screen first — Apple only allows web push for installed PWAs.

Click "Mark all read" at the top of the inbox, or click any individual notification — it'll be marked read when you navigate to the sighting it links to.

Yes — submitted sightings appear on the public map and feed by default. Your username, display name, and avatar are shown as the reporter. Your email is never public.

Sighting locations are precise (the map needs accurate coordinates to be useful). If you don't want a sighting tied to your home, manually pick a different drop point on the map — don't use the auto-filled GPS from a photo taken at home.

Every sighting, comment, and user profile has a Report option. On a sighting, click the ⋯ menu next to the title or "Report this sighting" below the engagement buttons. On a comment, click "Report" in the comment header. On a user profile (not your own), click the ⋯ menu in the header. We review every report within 24 hours.

Open their profile and click the ⋯ menu in the header → Block user. A blocked user can no longer follow you or see your sightings, and their reports are hidden from yours. Manage your block list at /me/blocked.

See our full Privacy Policy. Short version: account info (email, profile fields), sighting reports (media, location, details), and minimal device info. No tracking SDKs, no advertising, no cross-site cookies.

Check that you're signed in, your media uploaded successfully, and all required fields are filled: at least one photo or video, object shape, description, and location. The Reference URL field rejects malformed URLs — clear it and try again. If the form just hangs, check your browser console for any errors.

The map cache refreshes about every 5 minutes. Try a hard refresh (Cmd/Ctrl+Shift+R). If still empty, check your browser's console for network errors or try a different browser.

Try the email magic link if Apple or Google fails. Check your email (including spam) — sender is support@ufotracker.xyz. Magic links expire after 1 hour. If a link click lands on an error, try requesting a fresh link.

Photos cap at 8 MB and videos at 200 MB. Re-encoding (which strips EXIF) can occasionally fail on unusual file formats — try converting to standard JPEG/MP4 first. Uploads can also fail on flaky connections; try switching networks.

These are usually transient — refresh after 30 seconds. If it persists across refreshes, please contact support with the URL you were on and roughly what time it happened so we can check the server logs.