Skip to content

Update and rename docs/fileBytes.md to docs/developers/fileBytes.md #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DeveloperTryingToCodeLikeOtherOfThem wants to merge 1 commit into from
Closed

Update and rename docs/fileBytes.md to docs/developers/fileBytes.md #95

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/fileBytes.md → docs/developers/fileBytes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
## How Many Bytes Does a File Need?
## Bytes for a File

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep npm files list in sync with renamed doc path

After moving this document to docs/developers/fileBytes.md, the package manifest still lists the old path (package.json files entry docs/fileBytes.md), so the renamed doc is no longer shipped in published tarballs. I verified with npm pack --dry-run in this repo: docs/developers/fileBytes.md is absent from the output. Any consumer expecting this doc in the package will now miss it until the manifest is updated.

Useful? React with 👍 / 👎.

To determine how much memory a file requires, you need to consider its contents.
For example, in a text file, the size is determined by the number of characters (including spaces and punctuation). Each character typically requires one or more bytes of storage.
For other types of files, like images, the calculation is different. For an image on a 160x120 pixel screen, the total memory needed would be the total number of pixels (160 * 120) multiplied by the number of bytes required to store the color of each pixel (which depends on the bits per pixel, or BPP).
Loading