FAQ

No. Choose a file or try a sample on the homepage. The preview runs in your browser. An account is required only when you save that preview, import the file, or publish an endpoint.

No. A filter is part of one endpoint. GET, POST, PATCH, and DELETE on that same endpoint do not add to the published-endpoint count. A second endpoint is a separate published resource, even when it reads the same file.

You can still preview it when the browser can read that format and size. The preview is not stored as a hosted file. After you create an account, the page shows the file size and the Free per-file limit. The cheapest plan that can store the file is shown beside an option to choose a smaller file. A file that is exactly the limit is accepted when the rest of the quota allows it. Paying does not raise the browser preview ceiling.

The account stores your name, email, and password hash. If you continue from a preview in the same browser, FileToAPI stores the file name, the byte size, the field and filter settings, and up to five sample rows. That is a preview, not the full file. The full file is stored only when you import it and the plan allows it.

One request is one authenticated call to a published endpoint whose method is enabled. A filter is part of that same call. A rejected access key, a method that is turned off, and the call that finds the monthly quota already used are not counted. Drafts and homepage previews are not API requests.

They reset on the first day of each calendar month. A yearly subscription does not move that date. The Usage page shows the next reset.

No. The original file is counted once toward storage. Each published endpoint counts as one endpoint and can show a different set of fields.

No. Examples marked Example are illustrations. A curl command on a published endpoint in your account is a real request and counts toward the monthly quota.