Using Base64 from Apache commons
public byte[] encode(File file) throws FileNotFoundException, IOException {
byte[] encoded;
try (FileInputStream fin = new FileInputStream(file)) {
byte fileContent[] = new byte[(int) file.length()];
fin.read(fileContent);
encoded = Base64.encodeBase64(fileContent);
}
return encoded;
}
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
at org.apache.commons.codec.binary.BaseNCodec.encode(BaseNCodec.java:342)
at org.apache.commons.codec.binary.Base64.encodeBase64(Base64.java:657)
at org.apache.commons.codec.binary.Base64.encodeBase64(Base64.java:622)
at org.apache.commons.codec.binary.Base64.encodeBase64(Base64.java:604)
I’m making small app for mobile device.
You cannot just load the whole file into memory, like here:
Instead load the file chunk by chunk and encode it in parts. Base64 is a simple encoding, it is enough to load 3 bytes and encode them at a time (this will produce 4 bytes after encoding). For performance reasons consider loading multiples of 3 bytes, e.g. 3000 bytes – should be just fine. Also consider buffering input file.
An example:
Note that you cannot simply append results of
Base64.encodeBase64()toencodedbbyte array. Actually, it is not loading the file but encoding it to Base64 causing the out-of-memory problem. This is understandable because Base64 version is bigger (and you already have a file occupying a lot of memory).Consider changing your method to:
and sending Base64-encoded data directly to the
base64OutputStreamrather than returning it.UPDATE: Thanks to @StephenC I developed much easier version:
It uses
Base64OutputStreamthat translates input to Base64 on-the-fly andIOUtilsclass from Apache Commons IO.Note: you must close the
FileInputStreamandBase64OutputStreamexplicitly to print=if required but buffering is handled byIOUtils.copy().