App-to-Camera Recipe Transfer

Fuji X Weekly App-to-Camera Recipe Transfer now on Android!!

The wait is over! The Android version of the App-to-Camera Recipe Transfer Protocol (ATC RTP) is now complete, and available to you right now in the Fuji X Weekly App. You can send Fujifilm Recipes straight from the App to your Fujifilm camera. This feature has been in the works for a very long time, and was completed for Apple before Android. Since premiering on iOS, I’ve been working double time to get it out on Android.

I don’t want to rehash everything I already stated in the Apple release, but I will reiterate some of it. I highly recommend reading that article (click here) before using this feature. It basically works the same on Android as it does on Apple, so most of that will apply to you, too. One difference is that your Android phone must support USB host mode (USB OTG), which might need to be toggled on manually (most phones will do it automatically); to enable USB OTG, go to Settings → System/Connected Devices/Additional Settings (depending on your phone) → USB OTG/OTG Connection (depending on your phone). If you use an adapter, it must support data transfer.

Not every Fujifilm model is compatible, but most of the newer ones are. Specifically, as of this writing, you can use the ATC RTP with the Fujifilm X-Pro3, X100V, X-T4, X-S10, X-E4, X-T30 II, X-H2s, X-H2, X-T5, X-S20, X100VI, X-T50, X-M5, X-E5, X-T30 III, GFX100S, GFX50S II, GFX100 II, GFX100S II, and GFX100RF. Presumably all new cameras released in the future will also be compatible, but I won’t know for certain until they are available to test. Unfortunately, older models (such as X-Trans I, X-Trans II, X-Trans III, X-T30 and X-T3, X-series Bayer, and the first few GFX models) are not able to connect to the Fuji X Weekly App.

Very importantly, connecting your camera to any unofficial, unlicensed, unsupported program may void your camera’s manufacturer warranty. Fujifilm confirmed this with me. Please note that using the ATC RTP may void your camera’s warranty. Manufacturer warranties vary from country-to-country, and warranty laws vary from region-to-region, so read your specific warranty information very carefully, and research the laws that apply specifically to you. Some people are better protected than others; however, even if your warranty is technically voided, it’s possible that Fujifilm may decide to honor it anyway (or not realize it was voided) should something fail on your camera. It’s up to you if you want to take that risk, but my recommendation is to wait until after your camera’s warranty has expired (one or two years after purchase for most, but up to five years, just depending) before connecting to any unofficial, unlicensed, unsupported programs (pretty much any software that connects to your camera that’s not from Fujifilm or a major brand like Capture One or Adobe), including the Fuji X Weekly App. Whether you connect today, wait awhile before doing so, or never use this feature, that is a personal choice based on what you are comfortable with, having been well informed. I have connected all of my compatible cameras to the Fuji X Weekly App, including my brand-new GFX100RF, but that was my own decision based on my personal confidence in the App’s programming and in Fujifilm’s quality.

Whether on Apple or Android, if you’re having issues connecting your phone to your camera, the first place to look for help is the FAQ/Troubleshooting page within the Fuji X Weekly App. It’s a pretty good idea to read that before even starting, as there’s a lot of good information, some of which you’re likely to find helpful. I posted on Instagram how to configure your Fujifilm camera (click here) for ATC RTP, and you might find that helpful, too. I also have a short video showing this feature in action, which I’ve included below.

For those on Apple, a couple of quick final notes before ending this article. I just released an update with some small bug fixes and improvements, one related to the ISO setting on the camera. If your phone didn’t automatically update the Fuji X Weekly App, be sure to do so manually. This reminds me to remind you that the ISO on your camera needs to be at least the minimum for the Dynamic Range or D-Range Priority setting of the Recipe you want to transfer. For example, on fifth-generation cameras, Recipes that use DR400 will need a minimum of ISO 500, and fourth-generation need a minimum of ISO 640. For those with older iPhones that use a Lightning cable, it appears that the official Apple Lightning-to-USB 3 adapter (intended to connect the phone to cameras) is what’s required to get ATC RTP to work on your device. I have not tested this, it’s only from a handful of reports. I ordered an old iPhone and the adapter, and I hope to be able to confirm whether this does or doesn’t work by early next week.

Find more than 400 Fujifilm Recipes in the Fuji X Weekly App! Consider becoming a Patron subscriber to unlock the best App experience and to support Fuji X Weekly.

All photos in this article are ©️ Sahand Nayebaziz 2026, and are used with permission from the photographer. They were made with a Fujifilm X100VI using the Kodak Portra 400 Recipe.

Another Fuji X Weekly App Update!!

Posted on 17 Days Ago by Ritchie Roesch

The Fuji X Weekly App can now send Recipes straight from the App to your camera using a USB-C cable! Right now, this is only available on Apple, but it will be coming to Android within the next few months or so. If you haven’t read the announcement, there’s a bunch of important information in it, so I recommend starting there (click here)—it’s essential reading if you plan to use this feature.

The new Recipe transferring feature is called App-to-Camera Recipe Transfer Protocol (ATC RTP for short). A few days ago I discussed some of the known issues, but a couple of those have since been resolved, plus a new issue has come up, so I wanted to give a quick update. Let’s dive right in!

The two known issues that were fixed are 1) Recipes that use DR-Auto were transferring as DR100 instead of DR-Auto, and 2) a warning—for Recipes with Grain Off—that Grain was not able to be set when in fact it was set correctly (the error message itself was the bug). Those have been fixed on the latest Fuji X Weekly App update. If your phone didn’t automatically update the App, you may want to manually do so now. This is actually the second update since the new feature was released, so even if you haven’t encountered any issues yet, you may still want to double-check that you are running on the latest version.

The other known issue is that iPhones that use the Lightning plug (not USB-C) do not work with this feature; however, I’ve had several reports that using a Lightning-to-USB-C adapter will resolve the problem. I’ve not been able to try it myself to know for 100% certainty, but there have been enough reports that I’m fairly confident that this will work for you, too.

The new issue is a weird one. It might only affect those on iPhone 16, but I’m not completely certain about that. It seems that very few have encountered this problem, and it’s unlikely that it will affect you. If you are not able to get the phone to connect to the camera, and it always just says No camera connected even though you’ve tried everything, there is a potential solution. If you’ve encountered this rare problem, go to the Settings App on your iPhone, tap Privacy & Security (which is towards the bottom), select Files & Folders, and find the Fuji X Weekly App. Make sure that it is only in the list once (not twice) and that it is On (green); if not, toggle it/them Off/On until there is only one Fuji X Weekly option (not two) and it is On (green). If you find two Fuji X Weekly folders, when you toggle them one will disappear. This should resolve the problem, and you’ll be able to connect the camera to the phone.

Lastly, I wanted to give a quick update on the Instagram problem I had previously talked about. For those who missed it, Instagram removed my post announcing this new feature, claiming that I had violated their community standards, which obviously is not true or even remotely close to true. Restrictions were placed on my account, punishing me for something I didn’t do. I later learned that this is a systemic problem, and a lot of other people have had similar experiences, which is unfortunate. I requested that Instagram review their decision, and a few days later my post was reinstated, and the restrictions removed from my account; however, I never got an explanation. I still have no idea why they did this, but at least it’s been rectified.

Some App-to-Camera Recipe Transfer Protocol Issues + Instagram Really Sucks

Posted on 21 Days Ago by Ritchie Roesch

When I launched the new App-to-Camera Recipe Transfer Protocol (ATC RTP) in the Fuji X Weekly App a few days ago, which allows you to send Fujifilm Recipes from the App to your camera, I said, “I do anticipate some bug reports, and hopefully they’re all very minor.” So far, they’ve all been pretty minor, but I think you should be aware of them.

First, if you have an older iPhone that uses a Lightning plug, in order to get this feature to work, you will need a Lightning-to-USB-C adapter. I’ve had two reports that doing this works, although I don’t have a Lighting cable iPhone to test it with personally. Those who have older iPhones, let me know if the adapter works for you.

Second, if you are an App Patron and attempting to transfer Recipe sets, and your iPhone iOS is 18 or older (and not 26), the app crashes. This was identified pretty quickly and has already been fixed. So if this is happening to you, either update the iOS on your iPhone or update the Fuji X Weekly App to the latest version, either option will fix the issue, and allow you to transfer Recipe sets.

Third, and probably most notably for most people, is that DR-Auto Recipes set Dynamic Range in the camera to DR100 instead of DR-Auto. This was working correctly in a beta before launch, so I’m not sure why it’s not now. It’s likely an easy fix once the issue has been identified. Sometimes with apps, a small change somewhere affects something else that is seemingly unrelated, and that’s my best guess for this. I’m hopeful that a fix will be in by Wednesday or Thursday, maybe sooner, so be on the lookout for an App update.

Fourth, Recipes with Grain set to Off will transfer correctly, but give a (false) warning that Grain was not able to be transferred. The bug in this case is the warning itself, and not the transfer. The App will set Grain to Off in the camera, so just ignore that error message.

Right now, that’s it. But please, no matter how small, if you encounter any issues let me know. I’d love to get this running as cleanly as possible. Your feedback helps to improve it, and is greatly appreciated.

In related news, I posted about the App update on Instagram; however, the next day, Meta removed my post for supposedly violating community standards, and they put some restrictions on my account. Specifically, Instagram claims that the post made “unrealistic claims or promises about economic gain” and violated their rules on “financial fraud and scams.” Of course, that’s complete nonsense and just boggles my mind how they came to that conclusion. It could be that their AI bots are not very good and are flagging and banning innocent content, or it was falsely (and maliciously) reported by someone trying to disrupt or sabotage the announcement, or maybe something else entirely. I have no idea. But, whatever the reason, it wasn’t right or fair. I’m being punished by Meta for something I didn’t do. I have appealed, but who knows how long that takes or what the outcome will be. If it was from a false report, will that person be punished for making the claim should the appeal return in my favor? Probably not.

In my IG Stories, I posted about this situation, and asked if this has ever happened to anyone else. To my surprise, I received close to 50 messages from people who have had nearly identical issues. Some of them even shared with me what they posted that got removed, and it was normal (non-controversial) content, similar to most other posts on the platform, and not a violation of community standards whatsoever. In other words, this is a very widespread problem that could happen to anyone. Any and every post has the potential to be falsely flagged and deleted, and the author punished for the next 365 days. It’s not cool, but this is what you and I agree to when we sign up. Mark and company make massive profits off of our content, and we sometimes get treated like dirt for no other reason than we agreed to their terms of service.

There are two ways that I can respond to this. On one hand, I could stop using Instagram. Why am I allowing them to treat me this way? This seems like an abusive relationship that I’m enabling by staying. On the other hand, if it was removed due to malicious behavior by someone who dislikes Fujifilm, Recipes, or Fuji X Weekly (a competitive app developer, perhaps?), they win if I quit. I don’t even know if that’s the case, and I really hate to make any assumptions, so it might not be that at all. It might just be the terrible AI bots that Meta is using. So I’m not sure how to respond to this whole situation, other than to say Instagram really sucks, and I’m not happy with their platform right now. Maybe it’s a good time to consider an alternative.