How to easily extract arbitrary data from any file with just a pair of hexadecimal offsets

I recently had to extract data from a binary file and I was only provided with two hexadecimal offsets to obtain it with. Simply speaking, I had to pull out some data from an .ISO file (without mounting it…) and this “arbitrary data” would be a new file itself which could be read in other applications properly. Please make sure to backup anything you are throwing into the hex editor as even the slightest change could render an binary file completely unusable in it’s intended applications. This is critical for executables as they will likely break if you make a change.

  1. Download and install a “hex editor”. I like using Hex Fiend (Mac) as it just small and simple but wxHexEditor is also an attractive one for having lots of features and working across Mac, Windows and Linux. Both are free, open source and appear to be still maintained. The “hex editor” will allow us to manipulate binary data: look inside of a binary (non-ASCII) file and even make changes to it!
  2. Load up your file in your Hex Editor. I will use the example of “humansportsfestival02.iso” and the offsets that I told to extract are 0x1e1000 to 0x221000
  3. Using your hex editor, please visit the SECOND offset. In my case, this is 0x221000. I will go right ahead and delete all data AFTER this position. You will do that by selecting the contents of the file (like you would with a Word document) and deleting them.
  4. Now visit the FIRST offset value, in my case that is 0x1e1000 and select the contents of the file BEFORE this the same way by selecting the contents with your mouse or keyboard and then deleting them.
  5. Finally save your remaining data to a NEW file name (I chose to name mine: “Final Match Tennis Ladies.pce”) and you done!


The example that I am using is of course very specific but you can apply this to any of your own needs.





One response to “How to easily extract arbitrary data from any file with just a pair of hexadecimal offsets”

  1. […] and trailer, then save the data in between each occurence as new files, sort of like automating this process. I know next to nothing about coding so just give me advice in whatever language would be […]

Leave a Reply

Your email address will not be published. Required fields are marked *

forty five  ⁄  five  =