Version 2026.10.1.1
On a paid plan, any checked backup of a Minecraft Java world can now be drawn as a map you explore in the browser: around your spawn or the whole world, flat or in 3D. Each map is priced in credits, and the price is shown before you draw it. A map that can't be drawn gives its credits back. Maps are kept in your storage.
A world backup can now be as large as 32 GB once packaged, up from 5 GB. Every backup is still checked to make sure it is a complete, readable save, and that check now reads the backup where it is stored rather than copying it first, so even the largest one is checked in about eight minutes.
A big world is packaged in your browser before it is sent. If the browser runs short of room, the page asks to keep its data, which gives it more space; Firefox shows a prompt for this. Each backup is a full copy of the world and counts toward your plan's storage.
Version 2026.10.1
The bottom of every page now says plainly that Gameformatical is an independent service, not run by or connected with Mojang, Microsoft, Valve or Discord, and links to a new Notices page. That page credits where our game information comes from (Steam, IGDB and Wikidata) and whose trademarks the games' names are.
Files of 64 MB or more, on the Files page and as world backups, are now sent in pieces. If your connection drops part-way, only the piece that was on its way is sent again rather than the whole file, and the page shows how much has arrived. If an upload does stop, press the upload button again and it carries on from where it stopped.
A world backup also shows about how long it has left. An upload has 22 hours to finish, and if yours would take longer at your connection's speed, the page tells you straight away. Cancel, pressed while a backup uploads, now pauses it rather than throwing it away. Starting a new backup of a world replaces your own unfinished one, so an abandoned attempt no longer holds on to your storage. A large upload you delete, replace or leave unfinished no longer counts against your account's monthly malware-scanning allowance either, because none of it was ever scanned.
Programs that use the API can send large files in pieces too: ask for it when starting the upload, and the answer says how.
While an account's unpaid usage is past its grace period, or its monthly spend cap has been reached, starting a new upload — a file, a world backup or a voice recording — is refused with a message that says why and what resumes it: topping up for unpaid usage, and raising the cap or the start of next month for the cap. An upload that was already on its way still finishes, and your files stay available to download and to delete throughout.
Version 2026.9.28.3
A Factorio backup now shows a small picture of the save in its world's history: the view around your character when the game saved, from the preview the game itself keeps in every save it writes. Saves made by a dedicated server have no preview, so they show no picture. Pictures are sharper on high-resolution screens too.
A backup whose save has no picture no longer shows an empty grey square in its world's history, so the list doesn't look like a picture failed to load. Only backups with a picture show one.
Version 2026.9.28.2
Worlds keeps a history of your Factorio saves too. Choose a save from your Factorio saves folder, or drag it onto the page, and it is backed up exactly as the game wrote it. Each backup is checked for malware and then read to make sure the save is complete, and the page shows which version of Factorio saved it, whether it needs the Space Age expansion, and which mods it uses. Old saves count too, back to Factorio 0.14. The world's page explains how to restore a save, how Factorio can install the same mods for you, and how to bring a save from before 1.0 forward to today's game.
Once you keep more than one world, the Worlds page has a search box, and a choice of game when your worlds are of more than one. The list narrows as you type, and the page's address keeps your search, so reloading the page or coming back to it shows the same worlds.
On a phone, a backup's Delete button no longer runs off the edge of the page: its status, Download and Delete move onto a second line when they need to.
Version 2026.9.28.1
Worlds keeps a history of your Valheim worlds too, whether Valheim 1.0 saved them or an earlier version did. Choose your Valheim folder, or drag it onto the page, and pick the world to back up. Once a world has a backup, the page picks that same world for you next time, and says so if you choose a different one. Your characters are listed beside it and ticked, so they go into the backup with the world unless you untick them. If your world is saved to Steam Cloud instead, the page tells you so and shows you where to find it. Each backup is checked for malware and then read to make sure the world is complete, and the page shows the world's name, its seed and the characters it holds. The world's page explains how to restore a backup into Valheim's folders.
A backup that couldn't be read still counts toward your storage until it's removed a week later. Its row now says so, and that deleting it frees the space straight away. And if a new backup is refused because your storage is full while unreadable backups are holding some of it, the message says how much they're using, so you know what to delete. The link to compare plans that can come with that message now goes away as soon as you choose something else to back up.
Adding a backup now shows the steps for your own computer first, with a button that copies each folder's location, so you can paste it into Finder or File Explorer and drag the folder onto the page. The steps stay open until a world has a backup, fold away once one is sent, and after that the page reminds you which world your last backup was of.
If you choose the wrong folder, the page now says what's in it instead: a folder of several worlds, and which ones, or a folder with no world in it, when it opens the steps for the other place your game might keep its saves.
A world's name and each backup's label now have a pencil beside them: press it, type, and save, right where the name was. Renaming a world, or changing who can download its backups, saves without reloading the page, so a backup you're adding at the same time carries on.
On a Minecraft world, choosing a folder that isn't one world, such as the folder that holds all your worlds, now stops before anything is packaged or uploaded, and the page says why. Before, the whole folder was uploaded, only to be marked as not a readable world and deleted a week later.
Version 2026.9.28
Worlds keeps backups of your Minecraft: Java Edition worlds. Close the game, choose the world's folder (or drag it onto the page) and your browser packages it and uploads it straight to storage. Each backup is checked for malware and then read to make sure it is a complete, readable world, and the page says which version of the game it came from, with the world's own picture beside it when the world has one. Any backup can be downloaded again, with instructions for opening it as a copy alongside your other saves, and you can add notes to any backup.
Worlds live in your own account or in a crew's. In a crew, its admins add backups and every member can see the history. Only admins can download a world's backups at first; an admin can let every member download them, one world at a time, from the world's page. Backups can be up to 5 GiB and count against the storage of the account that keeps them: the free plan keeps 3 GiB, so a big world, or a long history of one, needs a paid plan. When a backup won't fit, the page says so before anything is uploaded, and links to the plans when a bigger one would hold it.
Your voice recordings still appear in Files, so you can always see what is using your storage, but you now play and download them from Voice recordings rather than from Files. In Files a recording no longer offers Download or Play, and its "Managed by Voice recordings" badge takes you straight there.
Files also stops offering what it could never do with the recordings folder: it shows a short note where Upload and New folder were, and it no longer offers to rename, move or delete that folder, or to move anything into it.
Creating, renaming or moving a folder so that it would share a name with another folder in the same place now tells you the name is taken, instead of failing with an error page.
Deleting the last file in a folder through the Files API could leave the folder refusing to be deleted as "not empty" even though it showed nothing. It is now empty when it looks empty.
Deleting a folder together with everything in it, through the Files API, now removes all of it or none of it. If something inside cannot be deleted there — your voice recordings, for example — nothing is removed and the reply says why. Before, part of the folder could already be gone, files included, by the time the delete stopped.
Your top-level Files folder can no longer be deleted through the API either, which the Files page never allowed.
If you already had a folder of your own called "Voice Recordings" in Files, new recordings were being saved into it, mixed in with your own files. Recordings now always go into their own folder, which Files marks as belonging to Voice recordings, and any already saved into your folder have been moved there. Your own files stay exactly where they were.
Version 2026.9.25
Campaigns can now have sessions — and so can a crew that has not proposed anything at all. "Is anyone about on Thursday?" is a perfectly good question, so a session does not need a campaign above it.
Everyone says whether they are going, not going or maybe, and can leave a note. No answer stays no answer — it is never counted as a no. Saying you can make Thursday is separate from being in for the campaign: you can be in for ten weeks and miss a week, and nothing assumes otherwise in either direction.
Every session has an "Add to calendar" button that downloads a file your calendar app can import. It carries the time, the title and a link back here — never an address, never anyone's email, and never a password.
When a campaign is ready to start, launching it puts its first session on the calendar. When it is over, ending it asks how it went — played it out, or stopped early — cancels any sessions that have not happened yet, and leaves everything that already happened exactly as it was. The confirmation tells you what it is about to do and what it deliberately leaves alone: your server keeps running, monitoring stays on, nothing is uninstalled and nobody loses access. If you pick the wrong outcome you can correct it later without reopening anything.
Thinking about starting something with your crew? Propose it as a campaign and find out who is actually interested before you pick a date.
Everyone says whether they are In, Maybe or Out, and can add a note. No answer stays no answer — it is never counted as a no. People can attach up to two conditions to their answer, like "only if it is a dedicated server", and if the crew later agrees something that clashes, they get asked whether they are still in rather than being quietly dropped.
There is a place to sort out the details too. Agree the things the crew argues about — who hosts, whether it is modded, whether there is a password — and anything you have not decided stays visibly undecided rather than defaulting to no. Anyone can suggest a mod or a modpack and say whether they want it, and the organizer publishes the agreed list. Add joining instructions and a campaign page becomes the one current answer to "what are we doing and how do I join?"
A campaign does not need a date or a server, and it never has to have one. Proposals you decide against go to an archive with the reason, so next time somebody suggests it you can see what happened before.
Version 2026.9.21.1
Your preferences now carry a schedule. Set quiet hours on your defaults card — the days and times you do not want to hear from us — and optional messages that would arrive then wait until the window ends. Account and security messages, and the notices that concern your account's standing, are sent regardless; the card says which.
Each channel we can reach you on — email, and the Discord @-mention in a crew's turn notifications — has a switch of its own, and in a crew you can set it differently from your default, or let that one crew reach you during your quiet hours. A turn still posts to the crew's channel during your quiet hours; it just does not ping you. Turning product updates off is now remembered against the address that received them, so it holds even if you change your address or sign up again.
Version 2026.9.21
Crew admins can now set when an announcement starts as well as when it ends, attach a link with its own label, and edit or reschedule an announcement from the manage page after publishing it. Each announcement shows whether it is upcoming, active or closed.
When you share a note with a crew you can now share it with the crew's admins only — a lobby password for the organisers, a reminder only they need. Admins see it, you still see and can edit it while you are a member, and nobody else in the crew does. "Make private again" takes it back like any shared note.
Every match a crew tracks — a Civ 6 game routed through a member's connection, an Old World game with its own URL — now takes notes the way your games, servers and recordings do. Members find them on the crew dashboard, under Tracked games, and admins on the crew hub beside each tracked game. A note is private until you share it with the crew; sharing keeps your name on it, and you can take it back.
The Game notes card on the Game connections page is gone. Any personal, crew or admin notes you had written there were moved to the matching tracked game with the same audience: a personal note is still private to you, a crew note is shared with that crew, and an admin note is shared with that crew's admins only. Everything you have written is on "My notes".
An announcement with a future start now appears on open pages when its time comes, without a reload. One that is closed, deleted or expires leaves open pages at once, and one that is still showing after it expired can be dismissed as usual. Editing an announcement updates it everywhere it is already showing, and anything you dismissed stays dismissed through edits and reschedules.
When several announcements are live, only the most important banner and the two newest toasts are shown; dismissing one reveals the next. This was the intended behaviour and was not working. The Announcements page now also shows each announcement's link.
An allow-list change whose sync was interrupted part-way — a deploy landing at the wrong moment, or the worker running out of memory — used to sit on "Applying your changes…" indefinitely until you made another change. It is now picked up again automatically within a few minutes.
An announcement addressed only to an account that was later deleted used to become visible to everyone once that account was gone. It is now removed with the account, and an announcement can no longer lose its last recipient by any route — the audience is narrowed or the announcement is deleted, never widened.
Version 2026.9.20
There is a Pricing page now, linked from the top of every page and the footer. It shows what each plan includes every month — files you can keep, downloads and streaming, servers monitored — how many friends a plan can gift a plan to, and what usage beyond the allowance costs from your credit balance. Every figure on it is read from the same place the billing itself reads, so the page and your bill can never disagree. Paid plans appear on it the day they go on sale; until then it describes the free plan.
It also says, in plain words, what happens if a balance runs out: the charge waits, new usage pauses after the grace period, monitoring you had switched on is turned off, storage keeps accruing for files you keep, and nothing is ever deleted for non-payment.
Press Play on an MP3, an M4A, an OGG or a recording made in a browser and it plays right there, in a bar-style player with the speed menu and "Set as default speed" in the bar — and, once the file has been measured, its waveform drawn along the timeline, filling in as it plays. Until now an audio upload had no Play at all: you could only download it.
Audio has its own default speed, separate from videos. The defaults card on your preferences page now has two rows, "Videos play at" and "Audio plays at", and the speed you had already chosen for videos is kept.
A file that belongs to a feature still plays from that feature's own page, where its controls are; the Files page shows it with its badge and no Play button.
If you sign up and never click the confirmation link, the registration now expires after seven days: the account is removed, and the e-mail address is free again — so you can simply sign up afresh, with a new invitation if sign-ups are by invitation. A confirmation link clicked after that says the registration has expired instead of failing, and confirming just before the cut-off still counts.
A few pages caught up with how accounts work now. The About page explains that everyone has a personal account and can also belong to crews, and links to the plans; the dashboard's settings link says "Account settings" on a personal account and "Manage crew" on a crew; and creating a crew is called that, not "New organization". The landing page points new visitors at the plans.
When something goes wrong during an in-page action — a search you have tried too often, a note the server would not take, a recording whose playback is paused for the account, or a page that no longer exists — the message now appears in the spot you were working in, where before nothing happened at all. Two confirmations that never asked ("Rotate relay token" and "Close the server" on a server's console) now do. Going Back after browsing folders on the Files page, or after switching an analytics window, returns you to the page as it is now rather than a stored copy.
The privacy policy has a new section on payments and billing: purchases go through Stripe, and card numbers never reach us; what we keep is your Stripe customer identifier, your plan and its status, your purchases and the credit ledger your balance is calculated from, and the daily usage totals a charge is explained by — amounts, never the content of anything. The section is on the Privacy page from the day the updated policy is published.
Every account has been able to see its metered usage — storage, downloads and monitored servers — on the Credits page for a while, marked "measured, not billed". From today it is billed: each plan includes a monthly allowance for each of the three, and only usage beyond it is charged, from the account's credit balance, at the rates shown on that page.
If an account's balance cannot cover a charge, the charge waits. After a few days of unpaid usage, new usage pauses — thumbnails, playback and switching on new monitoring — until the outstanding amount is settled. Nothing is ever deleted for non-payment, and your files stay yours to download.
Usage measured before today was never charged and never will be; the first billed day is the day this went live.
The "Voice recordings play at" setting on your defaults card is now "Audio and voice recordings play at": one default for the recording player and for audio files opened from the Files page. The speed you had chosen for recordings is kept — it is that setting, renamed, not a new one starting at normal speed.
A video shot upright made the player as tall as the video itself — several screens on a laptop, with the controls and the Notes button far below the notes they open. On a wide screen the player is now a widescreen frame, and a video of any other shape sits inside it with black bars, the way it does everywhere else. On a phone the player keeps the video's own shape, which fits the screen.
On My Top 10, dragging a game to a new place stopped working as soon as the list had changed once (the arrows kept working). Dragging works every time now, dragging a game within a group keeps it in that group, and a drag no longer sends the text of write-ups you have not saved yet along with the new order.
The "Notes (N)" count beside a game on your dashboard's Games widget used to be recounted from the notes on screen after you added or edited one, so a game with more notes than one page shows fell back to the page's worth. It now takes the total the notes panel itself reports, so the number is right however many notes there are.
When unpaid usage paused new activity on an account, the notice saying so stayed at the top of every page after the balance was settled — until somebody dismissed it by hand, a recovered account kept reading that its usage was paused. It now disappears the moment the account recovers, on pages that are already open too, and comes back only if the account runs out again.
Version 2026.9.16
You can now leave notes on the games in your crew's library and on the servers you can see — a plan for next session, a reminder about a restart, anything worth keeping beside the thing itself. A game's notes open from the Games widget on the dashboard; a server's sit on its own page. They are private until you share one with a crew that has that game in its library or that server linked, and a shared note stays with the crew even if the game or server is later dropped. Everything you have left is on "My notes"; a crew's shared notes are on its own page.
On a video, the control that makes the current speed your default now sits in the player's control bar next to the speed menu, instead of under the player. It reads "Default" on a narrow screen. Nothing else about it changed: picking a speed still affects that video only, and the control is greyed out while the speed is already your default.
Your chapters, markers and notes on a recording or a video now live inside the player. A Notes button in the player's controls shows how many there are and opens them — over the picture on a video, under the bar on a recording — and it works in fullscreen too. "Add note" beside it opens the list with the current time already filled in, so a marker lands where you were. Recordings show their chapters in a chapters menu in the controls, like videos do, and "Start over" sits in the controls when you had finished. Everything you could do before — edit and remove notes, share one with your crew, manage chapters if you are an admin — is inside the same panel.
Recordings play in the same player videos do. The waveform is the timeline: click or drag anywhere on it to jump, or use the arrow keys, Home and End once it has focus — and hovering shows the time under the pointer. The current and total time sit beside it, the speed menu offers the same choices as videos (0.5x to 2x), "Set as default speed" lives in the player's own controls, and a recording with chapters shows them in a chapters menu there too. Recordings that have not been measured yet still play; their timeline becomes draggable as soon as the length is known.
Version 2026.9.15
Videos in Files now have a speed menu in the player's controls, from 0.5x to 2x. Picking a speed changes that player and nothing else; to make the speed you have picked the one every video starts at, press "Set as default speed" under the player. Your default also lives on the Preferences page, under your defaults, where you can review or change it.
Voice recordings now have speed buttons beside the player, from 0.75x to 2x. Picking a speed changes that player and nothing else; to make the speed you have picked the one every recording starts at, press "Set as default speed" beside the buttons. Your default also lives on the Preferences page, under your defaults, where you can review or change it — it is kept separately from your video speed, so it never affects videos.
A recording or video now remembers where you were: open it again and it starts from there, on any device you sign in on, with a "Start over" link when you had finished. Crew admins can add chapters to a recording — typed one at a time or pasted as a list — and everyone in the crew can jump between them; a video's chapters also appear in its player's chapters menu.
While you listen you can leave yourself a marker at the current moment, or a plain note on the recording; these are private until you choose to share one with the crew you are in, and you can take it back again. Everything you have left is on your "My notes" page, and a crew's shared notes are on its own page.
Each voice recording now shows how long it is, a little after it lands — measured from the saved audio itself rather than reported by the browser, so the figure is the same one every listener gets. While a recording is still being processed the length is simply absent until it is known; on the rare recording whose exact length cannot be established, the row shows the length that could be verified with a "≥" in front of it rather than a guess. If you have the recordings page open, the length appears on the row by itself; you do not need to reload.
Each voice recording now shows the shape of its sound — taller where it is loud, flat where it is quiet — so you can see at a glance whether a memo is ten seconds of talking or two minutes with a long pause in the middle. It appears beside the Play button a little after a recording lands, like its length, and if you have the page open it shows up by itself.
Press Play and the waveform fills in as the recording plays, with the time riding along at the playhead. Point at it to see the time at that spot, and click anywhere on it to jump there. The normal player controls are still there underneath.
The waveform is measured from the saved audio itself, the same way the length is, so everyone who listens sees the same one. Recordings made before this change do not have one yet; they get theirs once they have been measured again.
Saving a recording now works the way file uploads do: the page asks for permission to save, sends the audio straight to storage, and then confirms it. The audio no longer passes through the application on its way there.
What that changes for you: a refusal — the account's storage is full, you are saving too fast, or the recording is in a format we cannot keep — arrives before the audio is sent rather than after, and a save interrupted by a dropped connection can be resumed by pressing Save again on the same take instead of recording it over. A recording is only listed once its audio has been confirmed; a take whose save never completed is cleaned up on its own.
Deleting a recording you only just saved is deferred for a short while in storage (it disappears from the list immediately), for the same reason file deletions are: it closes the window in which an interrupted save could have been quietly re-sent to a location that was meant to be gone.
A marker taken with "Now" inside the first second of a recording read 0:00, as if it had not been placed at all, and the time field was filled with plain seconds beside a hint written as 1:30. Marker and chapter times now show the milliseconds whenever the moment is not a whole second (0:04.949), "Now" fills the field in that same form, and editing a marker shows its time the way it reads in the list.
When a recording's details arrived while you were listening — its measured length and waveform landing a minute after you saved it, say — the player was rebuilt and playback stopped. The row now refreshes around the player, so it keeps playing. Deleting another recording, or a new one arriving in the list, no longer interrupts one you are listening to either.
On the Files page, the New folder, Rename, Move and Delete controls for folders now appear only for crew admins who can actually use them. Before, every member saw them, and pressing one as a member did nothing at all — no message, no change. Folder names and navigation are unchanged for everyone: members still see every folder and can open it.
The same rule now covers the file controls exactly: a control is shown only when the request behind it would succeed, so a button you can see is a button that works.
Every upload now goes the same way: the Files page asks for permission to upload, sends the file straight to storage, and then confirms it. The old route, where the file was sent through the application first, has been removed — including the API's multipart upload endpoint. API clients that posted a file body to `/api/assets/folders/<id>/upload/` must switch to the initiate → send → finalize sequence the Files page uses (`uploads/initiate` on the folder, then `uploads/finalize` on the file), which the API has offered for some time.
Two things get better for everyone. A refusal — for a full storage quota, for uploading too fast, or for an unsupported file — now arrives before a single byte is sent, instead of after the whole file has been transferred. And an upload interrupted by a dropped connection can be resumed: saving again picks up where it left off rather than starting a second copy.
Deleting a file you only just uploaded is now deferred for a short while in storage (the file disappears from your listing immediately). That is deliberate: it closes the window in which an interrupted upload could have been quietly re-sent to a location that was meant to be gone.
Version 2026.9.11
Your settings page now has a "Passkeys and security keys" card showing what you have set up — passkeys, security keys, an authenticator app — and a reminder to keep a spare. It replaces the unlabelled "MFA" button.
Resetting your preferences in a crew returns your own choices to your defaults and leaves in place anything an administrator has set for you specifically. Yours goes back to yours; theirs stays theirs.
Preference saves are also applied one at a time, so a crew's defaults stay consistent even when two administrators update them at the same moment.
If you have a passkey or security key, the second step of signing in now offers it first, instead of asking for a code you may not have. People with only an authenticator app no longer see a key button that could not work. Recovery codes still work as before.
When you add a key, the choice that used to be labelled "Passwordless" is now "Set up as a passkey" — tick it and that key can sign you in on its own, with no password. You can add as many passkeys and security keys as you like, and the two-factor page now says so.
After the second step of signing in, you can now choose to trust the browser you are on. If you do, subsequent logins from it can skip the second step for up to seven days. Changing your password or your sign-in methods asks again.
Trusting a browser only ever saves you the sign-in step. Adding or removing a passkey, security key or authenticator app, and viewing your recovery codes, always ask for one of your existing second factors first — on a trusted browser too.
Each account can now start a limited number of uploads, and send a limited amount of data, per minute. An upload over that pace is refused before anything is stored, with a message saying how many seconds to wait. Nothing already uploaded is affected, and a single large file is never refused for its size alone — the pace only bites once the minute's allowance is used up.
Once you had one security key, the "Manage" button under Security Keys showed an error page — which also meant there was no way to add a second key or a passkey. It now opens the list of your keys, with an "Add another" button.
Version 2026.9.10.1
Your voice recordings are stored as ordinary files, so they show up in Files alongside everything else. Until now the Rename, Move and Delete buttons were there too — and pressing Delete produced an error page rather than deleting anything, because the recording still needed the file.
Those files now carry a "Managed by Voice recordings" label and no edit controls. Delete the recording from the Voice recordings page instead, which removes the file with it.
They stay visible on purpose: they use your storage, and a listing that hid them would leave you unable to explain your own usage. If you would rather not see them while you work, the listing offers a link to hide them and always says how many are hidden.
Version 2026.9.10
Every account now has somewhere to put files. Upload screenshots, clips, maps or anything else, sort them into folders, and tag them so you can find them again. Images get thumbnails, and videos play in the browser without downloading them first.
Files belong to whichever account you upload them into — your own, where only you can see them, or a crew, where everyone in the crew can.
Two things worth knowing. Every upload is scanned before it becomes available, so a file is briefly unavailable after you add it; the page tells you when it is ready. And each account has 5 GB of storage, so an upload that would take you past it is declined rather than quietly filling up.
You can now record a voice note straight from your browser — nothing to install, no file to make first. Record it, listen back before you decide to keep it, and save it to whichever account you are in: your own, where only you can hear it, or a crew, where everyone in the crew can.
You can also say when the thing you are talking about happened, separately from when you recorded it. A note about last night's session sits under last night, not under the morning you got round to recording it.
Recordings can be up to ten minutes. Everyone in a crew can listen to that crew's recordings; for now, adding and deleting them is limited to the crew's admins.
Deleting a recording deletes the audio for good.
When one account's files are served to another account's members, the download can now be charged to the account whose member asked for it rather than to the account that owns the file. Nothing changes for your own files: those are billed to you exactly as before.
This is off until an account turns it on, and only a billing administrator can. The account whose files are being shared has to allow it too, so neither side can be charged for the other's decision.
Where a download cannot be matched to an account, it is now held aside and charged to nobody while somebody looks at it, instead of quietly landing on the bill of whoever owned the file.
Version 2026.9.8
Returning credits used to mean granting them as a fresh top-up, which recorded nothing about why they were returned and counted as a purchase in the revenue figures. There is now a proper refund: it records the reason and, when it reverses a specific charge, that charge — so a refund cannot quietly exceed what was charged, and a repeated attempt returns the same result instead of paying out twice.
The reason appears beside the refund on your credits page and in your data export, so you can see why credits moved without asking. Corrections that are not refunds have their own path, and neither can take a balance below zero.
Fixing how spending is matched to credits does not change balances that were already wrong. Those are now found and settled deliberately, one at a time: what the balance can still cover is taken back as an adjustment in your credit history with the reason attached, and anything already spent is written off rather than pursued.
Once a balance has been settled it stays settled — topping up afterwards does not reopen it.
You now have an account of your own, separate from any crew you belong to. It holds your own billing — your credits, your subscription — and your unshared work, and it is where you land when you sign up.
If you have been here a while, this is the crew that was made for you when you signed up: it has become your personal account, keeping its credits, its subscription and its history exactly as they were. Nothing moved.
A personal account is yours alone: it cannot have other members, and it cannot be turned into a crew. To play with other people, create a crew — your personal account stays separate. If you were invited to a crew you still land there, with your personal account waiting in the switcher alongside it.
One consequence worth knowing: because a personal account cannot have members, any invitations that were still outstanding on the crew that became yours have been withdrawn. Create a crew and invite them there.
A plan can now say who it is for — a person, a crew, or both — and the billing page offers you only the plans that apply to the account you are looking at. Previously there was one set of plans, and a personal account would have been shown a crew's.
The self-service billing portal follows the same rule, so the plans you can switch between there are the ones your account can actually have.
Until now the only crew you could have was the one made for you when you signed up, or one you were invited to — there was no way to start another. There is now a "New crew" button on your account settings page and in the account switcher.
Your existing account is untouched: creating a crew does not move anything out of it, and you can switch between them.
Premium access used to be decided by whichever crew you happened to be switched into, so a subscription stopped counting the moment you moved somewhere else. It now follows you: if any crew you belong to has an active subscription, or someone is sponsoring you, you get premium access whichever account you are working in.
Allowances are unchanged and still belong to the account they were bought for — a subscription on one crew does not give another one its storage, egress or monitoring allowance.
Any credits left on your personal account are forfeited when you delete it, and are not refunded. That was already the effect — the balance simply became unreachable — but nothing said so beforehand. The deletion page now tells you before you confirm, and the write-off is recorded in your credit history rather than the balance quietly ceasing to mean anything.
Your credit history itself is kept, as a financial record, in anonymized form.
Allowances were resolved by comparing your plan against the default one, and a plan that ranked at or below the default was ignored — so a subscriber could be given the same allowance as somebody who had never paid. Your plan now decides your allowance whichever one it is.
An active subscription on a plan this system does not recognise no longer falls back to the free allowance either; it keeps whatever it has been given while the mismatch is reported.
When credits were spent and a shorter-dated batch was added afterwards, the spending was sometimes charged to that newer batch instead. The older batch looked untouched, and credits that should have lapsed stayed in the balance instead — occasionally for good.
Spending is now matched to the credits that were genuinely available at the time it happened, so an expiry date means what it says. Balances already affected are not changed by this on its own; they are reported separately so they can be put right deliberately.
Switching to a crew, or accepting an invitation to one, did not check whether that crew was being stopped at the same moment. The switch could land you in a crew that no longer exists — the page would load with nothing in it and no obvious way back — and an invitation could be accepted into an account that had just stopped accepting members.
Both now settle against the crew itself, so whichever happens first wins cleanly: you either land somewhere real or are told the crew is no longer available.
If you had been invited to a crew but had not accepted yet, or your membership had been suspended, that crew still appeared in the switcher at the top of the page — and picking it gave you a permission error. Those crews are no longer listed, so everything the switcher offers now opens.
Billing emails follow the same rule: a suspended admin, or someone who never accepted their invitation, no longer receives notices about the crew's account.
The button on your profile and the page it leads to both said "Organization", which was neither the word used anywhere else here nor, now, true for most people. They say "Crew" when you are in one, and "Personal account" when you are in your own.
Permissions here are meant to be earned in the crew they are used in. On six of the file API endpoints they were not: someone who administered any crew could create, change and delete files through the API in every other crew they belonged to, even as an ordinary member.
They could only ever reach files in crews they were already in, so nothing was exposed to strangers — but the permission check now asks about the crew being acted in, as it already did everywhere else.
The list of your crews, read over the API, included crews you had been invited to but never joined, and crews you had been suspended from. It now matches what you can actually open, so a crew's name is not revealed by an invitation you never accepted or a membership that has since been withdrawn.
Version 2026.9.7
If there was a new version of the terms waiting for you, asking for the privacy policy sent you to the terms page instead of showing it.
That was backwards. The privacy notice is what explains how your information is handled, so it is exactly the thing you should be able to read before agreeing to anything. It now opens whenever you ask for it, whether or not you have accepted the current terms.
Version 2026.9.6.2
Release notifications now arrive one at a time — a new one replaces the last rather than stacking up behind it.
And if you have only just joined, you no longer arrive to a pile of notifications about changes made before you were here. The What's new page still has all of them whenever you want to look.
Version 2026.9.6.1
Notifications that point you somewhere — the one announcing a release, for instance — showed the address as plain text you had to retype. They now carry a real link you can click.
Version 2026.9.6
There is now a What's new page listing what we have released, linked at the bottom of every page. It starts here — this is the first entry, so it covers changes from now on rather than everything that came before.
If you would rather not check it, tick "Email me about new features" on your preferences page and we will send a short summary whenever we release something. It is off unless you turn it on, it is at most one email per release, and every one has an unsubscribe link. Sign-in links, password resets and crew invitations are separate and are not affected either way.