The data1~1E8B33C5/ folder is a little more interesting. The readme.txt contains nothing useful and the Budget.ymeta contains only metadata.Įverything on within this folder can be pretty safely ignored for now. Since I sync my budget to my phone via dropbox there’s also a conflicted file in there which can be ignored.
#Ynab 4 dropbox save zip file#
y4backup files is a zip file containing a metadata XML file and a monster of a JSON dump with every transaction I’ve ever made. rwxr-r- 1 jack jack 94 'Budget (x200'\''s conflicted copy ).ymeta'* I could start off by looking through all of the files from the budget I’ve been running for the last year, but it looks like an awful place to start. I fall into both of these categories.īy analysing the file structure and understanding it’s format, we can open a path to a continuation of the desktop app.
#Ynab 4 dropbox save full#
There are others that don’t wish to hand over their full transaction history to the YNAB cloud service. There are a lot of valid complaints from users that started their new way of life budget on a soon-to-be-deprecated piece of software without wanting to sign up to yet another recurring fee.
![ynab 4 dropbox save ynab 4 dropbox save](https://i.pinimg.com/originals/3a/79/9c/3a799c32ca61442214a134fae0b75947.jpg)
And there is no better time to look at documenting it.įollowing the community response to the subscription-based YNAB announcement and launch over the last few months has been interesting to say the least. There will be no YNAB 5 to turn the budget file structure on its head. A side effect of this move to the cloud is that the file structure is now set in stone. Reversing the YNAB file format - Part 1: JSON Structure Sep 13, 2016Īnyone reading this who is a user of the niche-but-somewhat-popular YNAB budgeting software will be well aware that YNAB has moved to a subscription pricing structure, meaning that YNAB 4 will be the final version of the ‘offline’ budgeting software.