<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>File-System on Commentary of Takao</title><link>https://takao.blog/en/tags/file-system/</link><description>Recent content in File-System on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/file-system/index.xml" rel="self" type="application/rss+xml"/><item><title>File System Access API: Powerful Local File Operations</title><link>https://takao.blog/en/web/file-system-access-api/</link><pubDate>Sat, 28 Dec 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/file-system-access-api/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post File System Access API: Powerful Local File Operations" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;For decades, web applications were limited to reading files through a clunky &lt;code&gt;&amp;lt;input type=&amp;quot;file&amp;quot;&amp;gt;&lt;/code&gt; element and had no reliable way to save changes back to the original file. The File System Access API changes this entirely. It enables web applications to read, write, and manage files and directories directly on the user&amp;rsquo;s local file system — with user permission, of course. This opens the door to building text editors, image editors, IDEs, and productivity tools that feel native.&lt;/p&gt;</description></item></channel></rss>