The default behavior for situations like that is to write the format you read in the first place. Weird that they would choose to do this!
Being tied to another company’s proprietary and idiosyncratic file format sounds like a terribly obnoxious burden for any piece of software: all the effort in reverse engineering the format and so on never yields quite the result you expect (Microsoft for example can’t even get their own formats right from one release to another, and they have loads of cash to throw at the problem), and any development time spent on it is time taken away from the actual image-making features of the app.