Fix Inkarnate 4K Export Failures: Black Maps and Missing Stamps

Inkarnate's high-resolution export is one of the main reasons people upgrade to paid plans. The ability to export at 8K or 16K resolution means crisp prints and detailed VTT maps. But that export button hides a minefield of technical problems that have frustrated users for years.

The symptoms vary. Your export starts but stalls at "10%," then instantly downloads a corrupted file. Half the map renders black while the other half looks fine. Stamps rotate and move to completely different positions. The exported image shows only the background with all your stamps missing. Sometimes the map editor itself crashes mid-export.

These problems have common causes. Understanding what's happening under the hood reveals why the standard advice works and what to try when it doesn't.

Why 4K+ Exports Fail

Inkarnate runs in your browser. Unlike desktop applications with direct hardware access, browser-based tools operate within strict memory and processing limits. When you export at high resolution, Inkarnate assembles your entire map at that resolution in memory before compressing it to a downloadable file. A 4K export requires roughly four times the memory of a 2K export. An 8K export requires four times that again.

Your browser allocates a limited amount of RAM and GPU memory to each tab. When Inkarnate requests more than that allocation allows, something breaks. The specific failure depends on which resource runs out first and how your browser handles the overflow.

Memory exhaustion during the rendering phase produces black sections. Your browser can't hold the entire image, so parts simply don't render. Memory exhaustion during the compression phase produces corrupted downloads or stalled progress bars. GPU memory exhaustion crashes the WebGL context entirely, which either freezes the editor or produces a blank canvas.

Map complexity multiplies the problem. A map with hundreds of stamps requires more GPU memory to composite than a map with sparse details. Dense forests, crowded cities, and heavily textured terrain all increase the memory footprint beyond what the raw resolution would suggest.

The Resolution Ladder Workaround

The most reliable fix comes from the Inkarnate community: open your map at a lower resolution, then export at your target resolution.

Here's the process. From your map list, click the three dots in the top right corner of the map thumbnail. Select "Open at Resolution" and choose 1K or 2K. Once the map loads at that lower resolution, go to File and Export. Select your target resolution (4K, 8K, or higher). The export should complete successfully.

This works because opening at a lower resolution reduces the baseline memory footprint. Inkarnate keeps less data in active memory during your editing session, which leaves more headroom for the export process. You trade preview quality for export reliability.

The downside: you can't see your map at full detail while editing. If you need to make final adjustments at high resolution, you'll need to close and reopen the map. But for finished maps where you only need the export, this workaround is fast and effective.

Disable Hardware Acceleration

Hardware acceleration uses your GPU to render graphics faster. In theory, this should help with large exports. In practice, some GPU drivers and browser combinations produce the opposite effect. Users have reported that disabling hardware acceleration allowed them to export at 16K when they couldn't even manage 4K with it enabled.

In Chrome, go to Settings, then System, and toggle off "Use hardware acceleration when available." In Firefox, go to Settings, General, scroll to Performance, uncheck "Use recommended performance settings," then uncheck "Use hardware acceleration when available." In Edge, go to Settings, System and performance, and toggle off "Use hardware acceleration when available."

Restart your browser completely after changing this setting. A simple refresh won't apply the change to existing WebGL contexts.

With hardware acceleration disabled, Inkarnate relies on your CPU for rendering. This is slower but more predictable. Your exports will take longer, but they'll actually complete. If time isn't critical, this trade-off is worth making for reliability.

Free Up System Resources

Browsers share your system's RAM and GPU memory with every other application. That YouTube video playing in another tab? It's consuming memory that Inkarnate could use for your export. Those twenty Chrome tabs you've accumulated? Each one takes a bite out of available resources.

Before attempting a high-resolution export, close everything else. All other browser tabs. Spotify. Discord. Whatever else is running. Check your system tray for background applications you forgot about. The goal is to give your browser maximum access to your system's memory.

For particularly large exports, consider restarting your browser entirely before opening Inkarnate. A fresh browser session has no accumulated memory fragmentation from previous sessions. This can make the difference between a successful 8K export and a black rectangle.

If you have 8GB of RAM or less, high-resolution exports will be consistently difficult. Users report that 16GB is enough for 16K exports, though it's close to the limit. With 32GB, you're unlikely to hit memory constraints regardless of map complexity.

The Stamp Movement Bug

A separate issue affects exports at 6K resolution and above. Stamps in certain regions of the map (often the top right) rotate and move to completely different positions in the exported image. The map looks correct in the editor, but the export shows stamps displaced.

This is a rendering bug, not a memory issue. The workaround is to open the map at 4K resolution before exporting. This seems to reset whatever internal state causes the misalignment.

If stamps still move after trying the resolution workaround, export at 4K instead of your target resolution and upscale in image editing software. A 4K export upscaled to 8K will be slightly softer than a native 8K export, but the stamps will be in the correct positions. For most use cases, including print and VTT, the quality difference is negligible.

The Disappearing Stamps Bug

Another variant: exporting produces only the background texture with all stamps missing. This typically affects specific maps rather than your entire library. Other maps export normally at the same resolution.

If you encounter this, first try the resolution ladder workaround. Open at 1K, export at your target resolution. If that fails, try exporting at incrementally lower resolutions until you find one that works. A 2K export with all your stamps is more useful than an 8K export of just the background.

For maps that refuse to export correctly at any resolution, use the "See Image" feature from your map folders. This displays your map at saved resolution in your browser. Take a screenshot or use your browser's "Save Image As" function. The quality won't match a proper export, but you'll get a complete image.

Different Layers at Different Resolutions

Some users report that stamps appear on different layers in their exports depending on the resolution. A stamp that sits behind a tree at 2K might appear in front of that same tree at 4K. This breaks carefully composed scenes where layering matters.

The cause relates to how Inkarnate composites flattened stamps. The workaround is to use the "Lock" function on stamps in your editor before exporting. Locked stamps maintain their z-order (front-to-back positioning) more reliably across resolution changes.

If you notice layer inconsistencies in your exports, go through your map and explicitly set the layer for each stamp using the Foreground, Background, and Top layer options. Stamps with explicit layer assignments tend to export more consistently than stamps placed with default layering.

Browser-Specific Issues

Chrome handles WebGL differently than Firefox, which handles it differently than Edge. If exports fail consistently in one browser, try another.

Chrome tends to be more aggressive about terminating memory-hungry tabs. This protects system stability but can cut off Inkarnate mid-export. Firefox often allows processes to consume more memory before intervention, which can mean the difference between a completed export and a crashed tab.

Try exporting in Firefox if Chrome fails. Try Edge if Firefox fails. Some users report that Brave (a Chromium-based browser with different default settings) handles large exports better than Chrome despite sharing the same rendering engine.

Whichever browser you use, make sure it's updated. WebGL implementations improve with each browser version, and export bugs sometimes resolve after an update.

When Nothing Works

If you've tried everything and your map still won't export correctly, you have fallback options.

Export at a lower resolution. A clean 2K export is better than a corrupted 8K export. For VTT use, 2K is often sufficient. For print, you can upscale with software like Topaz Gigapixel or similar AI upscalers. The results won't be identical to native high-resolution exports, but they'll be usable.

Export in sections. Pan to different regions of your map and take screenshots at maximum browser zoom. Stitch the screenshots together in image editing software. This is tedious but produces complete results when the normal export fails.

Contact Inkarnate support. The bug tracking forums show that the team actively investigates export issues. Your specific problem might have a known solution that isn't widely documented, or your bug report might help them fix the issue for everyone.

Prevention: Build with Export in Mind

If you haven't started your map yet, or if you're planning a future project, some upfront decisions reduce export problems later.

Start at your target export resolution. Creating a map at 4K and exporting at 4K is more reliable than creating at 1K and exporting at 4K. The map stores reference data differently depending on the working resolution.

Limit stamp density in problem areas. The top-right region of maps seems particularly prone to the stamp displacement bug. If you're creating a complex map, consider putting your densest details in other areas.

Save frequently and save versions. Before attempting a high-resolution export, save a copy of your map. If the export process corrupts something (rare but documented), you can revert to the saved version.

Test exports early. Don't wait until your map is finished to discover export problems. Do a test export at your target resolution when the map is 25% complete. If issues appear, you can adjust your approach before investing more hours.

The Technical Reality

Browser-based applications face hard constraints that desktop applications don't. Inkarnate does impressive work within those constraints, but the constraints are real. High-resolution exports push against the limits of what browsers can reliably handle.

The workarounds exist because the Inkarnate community has tested hundreds of configurations and reported what works. The resolution ladder, disabling hardware acceleration, closing background applications: these aren't elegant solutions, but they solve the problem for most users most of the time.

If you're using Inkarnate professionally and need reliable high-resolution exports, consider keeping a dedicated browser profile with optimal settings: hardware acceleration disabled, no extensions, no bookmarks, no logged-in accounts consuming background resources. Open this profile only for Inkarnate exports. The friction of switching profiles is minor compared to the frustration of failed exports.

Your maps deserve to exist outside Inkarnate's editor. These workarounds get them there.