Most failed edits come down to four things: a one-off processing glitch, an unsupported file type, a subject AstroEditor AI isn’t built for, or an image with too little usable data. Work through them in that order. The first is fixed by simply resubmitting, and it accounts for a good share of cases.
Quick version
- Resubmit the image once before anything else
- Check what your file actually is, not just its extension
- Confirm it is a deep sky image, not a landscape
- Open it and look at the data yourself
Should I just try again? #
Yes, and do this before anything else. Resubmit the same image for editing and see whether the problem repeats.
Processing occasionally has an off run, and a single odd result often clears on a second attempt. It costs you a couple of minutes and rules out the simplest explanation.
If it fails the same way twice, stop resubmitting. Two identical failures point at the image itself rather than the processing, and the rest of this page is about finding out which part of the image is the problem.
Is it the file type you uploaded? #
Very often, yes. The most common version of this is taking an already-edited JPEG, converting it to TIFF, and uploading that.
Converting a file does not restore what the original format threw away. A JPEG has already been compressed and stretched, so the tonal headroom is gone. Saving it as a TIFF produces a file with a TIFF extension and JPEG-grade data inside, and processing has nothing left to work with. If the JPEG has been exported from a smart telescope app, it often has banners and other information added to it that throws off the editing, causing it to fail.
The same applies to screenshots, phone photos of a screen, and images pulled from social media. All of them are already compressed and no good for further editing.
The fix: go back to your original stacked output and upload that. If you stacked in a smart telescope app, export the stacked file rather than the preview image. If you no longer have the original, the image cannot be recovered and you will need to reprocess from your subs.
Is it the right kind of image? #
AstroEditor AI is built for deep sky objects: nebulae, galaxies, star clusters. It is not designed for wide-field Milky Way shots, nightscapes, or anything with a landscape or foreground in the frame.
Those images break the assumptions processing relies on. A deep sky frame is mostly dark background with point stars and diffuse nebulosity, and the models are trained to read that. A treeline, a horizon, or a foreground rock is a large bright structure that gets treated as signal, and the result is either a poor edit or a failure.
| Image type | Suitable |
|---|---|
| Deep Sky Objects – Nebula, galaxy or cluster, full frame | Yes |
| Smart Telescope stack of a deep sky target | Yes |
| Milky Way wide field with horizon | No |
| Nightscape with foreground | No |
| Star trails | No |
| Planetary or lunar | No |
The fix: crop out the foreground if the deep sky portion of the frame is large enough to stand alone. If the whole image is a landscape composition, it is outside what the tool does, and a general photo editor will serve you better.
How do I check the image data itself? #
Open the file and look at it. Use the AstroEditor Image Viewer app, or any image editor that handles your file format.
You are checking three things. Can you see stars? Does the frame look like a coherent image rather than noise or banding? Is there actually something there, or is it near enough a black rectangle?
Files do get corrupted, particularly during transfer from a telescope or camera to a computer. And a short session on a faint target can produce a technically valid file with so little signal in it that there is nothing to enhance. Processing needs data to work with, and when there isn’t any, it fails rather than inventing detail.
The fix: if the file looks corrupted, re-export it from your stacking software. If it looks thin, the answer is more integration time rather than more processing. An hour on target will do more for your result than any edit.
Common mistakes #
- Resubmitting repeatedly — if it has failed twice the same way, a third attempt will not change anything. Move on to checking the file.
- Trusting the file extension — a TIFF converted from a JPEG is still JPEG data. Check where the file actually came from.
- Uploading a stretched image — heavily edited images have already had their data and tonal range compressed. The system is designed to work from linear data. Start from your stacked output.
- Expecting processing to fix thin data — no edit recovers signal that was never captured. Twenty minutes on a faint galaxy will not produce a clean image no matter how much you edit it.
- Not looking at the file — most causes are visible in ten seconds if you open the image before you troubleshoot.
Still stuck? #
Send us the image. If you have worked through the checks above and it still fails, email the file to support@astroedit.co.uk and we will look at it directly.
We can usually tell fairly quickly whether it is a fixable problem with the file or a limitation of the data, and we will tell you which. If it would be more useful to talk it through, you can also ask to book a call with us and we will go through your images together and look at what would improve them at the capture stage.
If the same problems keep recurring across different images, that usually points at something in your capture or stacking workflow rather than any single file. The Beginner to Pro Training covers the full sequence from acquisition through to a finished edit, and the Smart Telescope Masterclass goes deeper on getting clean data out of a Seestar or Dwarf.
Frequently asked questions #
Can I upload the JPEG my smart telescope app produced? #
You can, but results will be limited. The app JPEG is a preview with compression and stretching already applied. Export the stacked file from the app instead, which keeps far more of the original data intact.
How much integration time do I need before editing is worth it? #
Around 30 minutes for a bright target like the Orion Nebula, and an hour for anything faint. Below that there is often too little signal for processing to improve, however good the edit.
My image processed but looks wrong rather than failing. Same causes? #
Largely yes. A poor result and an outright failure usually share a root cause, most often file type or subject matter. Work through the same four checks in the same order.
Related guides #
- What is image stacking in astrophotography?
- Which file formats does AstroEditor AI accept?
- Exporting stacked files from your smart telescope
Not signed up yet? Try AstroEditor AI free, or see what Pro adds.
