Submit Your Track

Share your custom PolyTrack creation with the community.

All submissions are reviewed before publishing. Email is required so we can send the result: accepted tracks get a publish link, declined tracks get a short revision note, and improved versions can point reviewers back to the original track.

Submission Type

We need a working email to send your publish link, revision note, or rejection reason. We do not show it publicly.

Not sure how to take the right screenshot?

Expand the How to Submit a Track Correctly guide at the top of this page for a step-by-step walkthrough with screenshots.

Describe at least 2–3 specific features. Mention what makes the track unique, the hardest section, and what skill it tests.

Upload a zoomed-out editor screenshot that shows the full track layout. Do not use driving-camera screenshots, partial close-ups, or unrelated images.

A video showcase helps get your track featured!

Submission Guidelines

  • • Make sure your track code works before submitting
  • • Include a full overview image captured from the editor after zooming out
  • • Provide an accurate difficulty rating
  • • Write a clear, descriptive title
  • • Include tips or notable features in the description
  • • If this is an update, include the original track link or title and what changed
  • • Use a working email so we can send the review result
  • • Original creations only - no copied tracks

What Happens After You Submit

  1. We check whether the code imports and the track matches the submitted description.
  2. Promising tracks are edited for title, description, category, and preview quality before publishing.
  3. We send either the published track link or a short note on what to improve.
  4. You can submit an improved version later by selecting the update option and explaining what changed.

Recently Published Tracks

Strong submissions can become public track pages with creator credit and a shareable link.

Review Criteria

  • Importable: The code must import and load correctly in the current version.
  • Clear description: Include at least two specific features, such as hairpin chains, aerial landings, or short-sector rhythm.
  • Accurate difficulty: The selected difficulty should match the actual driving experience.
  • Good naming: The title should reflect the gameplay or theme, not random characters.

Common Rejection Reasons

  • The code cannot be imported or fails to load.
  • The description is too short, inaccurate, or clearly template-generated.
  • The difficulty rating is far from the actual experience.
  • The submission is a duplicate or highly similar to an existing track.
  • The track contains policy-violating or inappropriate content.