--- title: Announcing Change History for Firebase Remote Config description: Firebase Remote Config now includes change history, letting teams see who changed parameter and condition values, when, and how (Firebase Console or REST API).... canonical: https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Announcing Change History for Firebase Remote Config | daily.dev og:description: Firebase Remote Config now includes change history, letting teams see who changed parameter and condition values, when, and how (Firebase Console or REST API).... og:url: https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn og:image: https://api.daily.dev/og/posts/ip3ZDV7NN.png og:image:alt: Announcing Change History for Firebase Remote Config og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Announcing Change History for Firebase Remote Config **[Firebase](https://daily.dev/sources/firebase-blog)** · 4 min read · 0 upvotes · 0 comments ## Summary Firebase Remote Config now includes change history, letting teams see who changed parameter and condition values, when, and how (Firebase Console or REST API). Firebase retains up to 300 versions for 90 days, and users can roll back to a previous version with a single click, which creates a new version based on the rollback. The feature is available in both the Firebase Console and the Remote Config REST API, with code samples provided for Node.js, Java, and Python. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How many versions of Remote Config values does Firebase retain and for how long? Firebase saves up to 300 versions of a project's Remote Config values, retained for up to 90 days. Each version records the parameter and condition changes, who made them, when they were made, and whether they came from the Firebase console or the REST API, enabling one-click rollback to any prior version. _Developers tracking config changes across teams can follow platform capability updates like this on daily.dev._ ### What happens when you roll back to a previous version in Firebase Remote Config? Rolling back to an earlier version does not simply restore history; it creates a brand new version based on the rolled-back values. For example, rolling back from version 37 to version 36 produces a new version 38, which carries the same conditional values as version 36, such as a parameter targeting 10% of users. _Teams coordinating remote config rollouts can keep up with tooling changes like this via daily.dev._ ### Can I access Firebase Remote Config change history through an API instead of the console? Yes, change history for Remote Config is accessible through the Remote Config REST API in addition to the Firebase console. A listVersions endpoint (with a pageSize parameter) returns the most recent versions, and example implementations are available for Node.js, Java, and Python in Firebase's quickstart GitHub repositories. _Developers automating config audits can track API-driven workflow changes like this on daily.dev._ ## Similar posts on daily.dev - [Optimize your Firebase Remote Config usage](https://daily.dev/posts/optimize-your-firebase-remote-config-usage-woddfd7ym) · Firebase · 1 upvotes · 1 comments - [Dynamic configuration in Java with Server-Side Firebase Remote Config](https://daily.dev/posts/dynamic-configuration-in-java-with-server-side-firebase-remote-config-yvb4sfjnd) · Firebase Developers · 0 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#rest-api](https://daily.dev/tags/rest-api), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Announcing Change History for Firebase Remote Config","url":"https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn"},"datePublished":"2026-08-23T12:19:24.519Z","dateModified":"2026-08-23T12:35:43.939Z","description":"Firebase Remote Config now includes change history, letting teams see who changed parameter and condition values, when, and how (Firebase Console or REST API)....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,rest-api,firebase","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Announcing Change History for Firebase Remote Config"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/announcing-change-history-for-firebase-remote-config-ip3zdv7nn#faq","mainEntity":[{"@type":"Question","name":"How many versions of Remote Config values does Firebase retain and for how long?","acceptedAnswer":{"@type":"Answer","text":"Firebase saves up to 300 versions of a project's Remote Config values, retained for up to 90 days. Each version records the parameter and condition changes, who made them, when they were made, and whether they came from the Firebase console or the REST API, enabling one-click rollback to any prior version. Developers tracking config changes across teams can follow platform capability updates like this on daily.dev."}},{"@type":"Question","name":"What happens when you roll back to a previous version in Firebase Remote Config?","acceptedAnswer":{"@type":"Answer","text":"Rolling back to an earlier version does not simply restore history; it creates a brand new version based on the rolled-back values. For example, rolling back from version 37 to version 36 produces a new version 38, which carries the same conditional values as version 36, such as a parameter targeting 10% of users. Teams coordinating remote config rollouts can keep up with tooling changes like this via daily.dev."}},{"@type":"Question","name":"Can I access Firebase Remote Config change history through an API instead of the console?","acceptedAnswer":{"@type":"Answer","text":"Yes, change history for Remote Config is accessible through the Remote Config REST API in addition to the Firebase console. A listVersions endpoint (with a pageSize parameter) returns the most recent versions, and example implementations are available for Node.js, Java, and Python in Firebase's quickstart GitHub repositories. Developers automating config audits can track API-driven workflow changes like this on daily.dev."}}]} ```