diff --git a/README.md b/README.md
index 8950641..c4bd2b7 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,65 @@
 # tinytoml
 [![Run Tests and Code Coverage](https://github.com/FourierTransformer/tinytoml/actions/workflows/test-and-coverage.yml/badge.svg)](https://github.com/FourierTransformer/tinytoml/actions/workflows/test-and-coverage.yml) [![Coverage Status](https://coveralls.io/repos/github/FourierTransformer/tinytoml/badge.svg?branch=refs/pull/1/merge)](https://coveralls.io/github/FourierTransformer/tinytoml?branch=main)
+
+tinytoml is a pure Lua [TOML](https://toml.io) parsing library. It's written in [Teal](https://github.com/teal-language/tl) and works with Lua 5.1-5.4 and LuaJIT 2.0/2.1. tinytoml parses a TOML document into a standard Lua table using default Lua types. Since TOML supports various datetime types, those are _by default_ represented by strings, but can be configured to use a custom type if desired.
+
+tinytoml passes all the [toml-test](https://github.com/toml-lang/toml-test) use cases that Lua can realistically pass (even the UTF-8 ones!). The few that fail are mostly representational:
+- Lua doesn't differentiate between an array or a dictionary, so tests involving _empty_ arrays fail.
+- Some Lua versions have differences in how numbers are represented
+- tinytoml currently support trailing commas in arrays/inline-tables. This is coming in TOML 1.1.0.
+
+Current Supported TOML Version: 1.0.0
+
+## Installing
+You can grab the `tinytoml.lua` file from this repo (or the `tinytoml.tl` file if using Teal)
+
+## Parsing TOML
+
+### `tinytoml.parse(filename [, options])`
+With no options, tinytoml will load the file and parse it directly into a Lua table.
+
+```lua
+local tinytoml = require("tinytoml")
+tinytoml.parse("filename.toml")
+```
+It will throw an `error()` if unable to parse the file.
+
+### Options
+There are a few parsing options available that are passed in the the `options` parameter as a table.
+
+- `load_from_string`
+
+  allows loading the TOML data from a string rather than a file:
+  ```lua
+  tinytoml.parse("fruit=banana\nvegetable=carrot", {load_from_string=true})
+  ```
+
+- `type_conversion`
+
+  allows registering a function to perform type conversions from the raw string to a custom representation. TOML requires them all the be RFC3339 compliant, and the strings are already verified when this function is called. The `type_conversion` options currently supports the various datetime types.
+  - `datetime` - includes TZ
+  - `datetime-local` - no TZ
+  - `date-local` - Just the date (2024-10-31)
+  - `time-local` - Just the time (12:49)
+
+  For example, if you wanted to use [luatz](https://github.com/daurnimator/luatz) for handling datetimes:
+  ```lua
+  local luatz = require("luatz")
+  local type_conversion = {
+    ["datetime"] = luatz.parse.rfc_3339, -- realistically you would want to handle errors from whatever module
+    ["datetime-local"] = luatz.parse.rfc_3339
+  }
+  tinytoml.parse("a=2024-10-31T12:49Z", {type_conversion=type_conversion})
+  ```
+
+  or just use your own method:
+  ```lua
+  local function my_custom_datetime(raw_string)
+    return {["now_in_a_table"] = raw_string}
+  end
+  local type_conversion = {
+    ["datetime"] = my_custom_date,
+    ["datetime-local"] = my_custom_date
+  }
+  tinytoml.parse("a=2024-10-31T12:49Z", {type_conversion=type_conversion})
+  ```