Services

Game Porting

Bring your existing game to mobile, desktop or the browser. We adapt controls, interfaces, performance and platform integrations for the players you want to reach.

XGameDev provides game porting services for studios, publishers and product owners with an existing game. We work primarily with Unity across iOS, Android, Windows, macOS and WebGL, with HTML5 conversion work for legacy browser games.

A port needs to preserve the game while making it practical to play on the destination platform. We review the source code, controls, interface, assets and external services, then agree what can be reused and what needs to change.

Platforms we port between

Mobile to desktop

Bring an iOS or Android game to Windows or macOS. We adapt touch interactions for keyboard, mouse and controller where required, rework menus for larger screens, and review resolution, window behaviour and save locations. Mobile-only SDKs, purchases and account flows need a desktop plan. Steam integration and release preparation can be included in the scope.

Desktop to mobile

Adapt a Windows or macOS game for iOS and Android. The work can include touch controls, smaller-screen layouts, readable text, graphics settings and asset optimisation. We define device targets and test memory use, loading, frame rate and behaviour when the app is paused or resumed. See our Unity mobile development service for mobile integrations and release support.

Mobile or desktop to WebGL

Make an existing Unity game playable from a browser link. We assess plugins, networking, input, audio, save behaviour and loading before setting the port's scope. Browser delivery may need changes to code, assets or backend connections, particularly where the original game depends on native platform features.

We agree the supported browsers and devices, download and memory budgets, and hosting setup. Mobile browser testing is a separate requirement from testing an installed iOS or Android app. Unity documents the relevant Web platform limitations; the assessment uses the version your project will ship with.

WebGL to desktop or mobile

Turn a browser-delivered Unity game into an installed Windows, macOS, iOS or Android build. We review browser-specific integrations, replace web-only dependencies where needed, and adapt input, local storage and the release process. Offline play needs an agreed design if the existing game relies on a server. For a non-Unity HTML5 game, we first assess whether packaging or a rebuild suits the target.

iOS to Android, and Android to iOS

Extend an existing mobile game to the other platform. We review native plugins, permissions, purchases, sign-in, notifications and build configuration, then test the agreed device range. Platform accounts, signing and store materials form part of release planning.

Windows to macOS, and macOS to Windows

Add a second desktop target to an existing Unity game. Work can include replacing platform-specific plugins, reviewing graphics and file handling, adapting input, and preparing builds for the agreed distribution channel. The assessment defines the operating systems and hardware to support.

Flash to HTML5

Rebuild legacy Flash games and interactive activities for modern browser delivery. XGameDev's experience includes 500 Flash-to-HTML5 conversions. We identify the gameplay, artwork, audio and integrations to retain, then adapt the interaction for the destination browser and input methods. Our Construct development service covers the implementation and legacy-project options.

Porting experience: Old as Dirt

For Old as Dirt, CoRE Learning Foundation's classroom Earth Science game, we moved an existing Unity project from Windows and Mac delivery to WebGL. The work included bug fixes, asset handling, feature development and adapting multiplayer activities for single-player use.

The browser product also needed APIs, data storage, an administration app and automated deployment. That project shows why the porting scope needs to cover both the game and the systems around it.

From source review to a tested build

  1. Review the project. Check the engine version, source availability, asset licences, plugins and current build. Record platform dependencies and the features that must survive the move.
  2. Prove the difficult parts. Test uncertain integrations or performance on the target device before committing to the full adaptation.
  3. Adapt and profile. Update controls, layouts, assets and platform services. Review playable builds against agreed functionality, loading and performance targets.
  4. Prepare release and handover. Supply the agreed builds, source changes, build instructions and test notes. Define responsibility for hosting, store accounts, submission and later updates.

To start, share the current platform, intended destinations, a playable build or video, engine version and any deadline. Include save-data, multiplayer and purchase requirements early. Our project brief guide can help you assemble those details.

Can you port a mobile game to desktop or a desktop game to mobile?

Yes. We work with existing Unity projects to adapt gameplay, controls, interfaces, performance and platform services for Windows, macOS, iOS and Android. We review the source, dependencies and target devices before agreeing the port's scope.

Can my Unity game run in a browser with WebGL?

We assess the project before committing to a WebGL port. Native plugins, networking, memory use, download size and browser behaviour can require changes. The scope identifies the Unity version, supported browsers and devices, hosting requirements and any feature changes.

Do you need the original source code?

For an existing Unity port, we normally need the project source, assets and permission to use them, plus a working reference build. For legacy Flash content, recordings and available assets can help define a rebuild when the original source is incomplete. We assess what is recoverable before estimating.

Will player progress and purchases carry across platforms?

Only where the account system, data access and platform rules allow it. Save migration, shared accounts, multiplayer compatibility and purchase entitlements need explicit design and testing. We agree which data and features must carry over during the assessment.

How much does game porting cost, and how long does it take?

The main factors are source quality, engine version, plugins, controls, content size, performance targets and release integrations. Share a build and your source and destination platforms so we can identify the work, estimate it and agree milestones.

Where should your game run next?

Send a build or video, the current platform, your target platforms and any launch deadline. Jacques or Melanie will reply within one business day.

Discuss your game port