> For the complete documentation index, see [llms.txt](https://dazhizhong.gitbook.io/pixray-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dazhizhong.gitbook.io/pixray-docs/docs/image-filters.md). # Image filters ### `filters` > Default: `None` `filters` can either be `"lookup"`, `"wallpaper"`, or `None`. Lookup uses the `ColorLookup` class, which, for a single specified palette, maps colors on the generated image (output) to the nearest color on the palette. This is a hard constraint and is performed first, before any losses or prompt evaluations are made. The syntax in which the palettes are created are best demonstrated in the colab demo [here](https://colab.research.google.com/github/dribnet/clipit/blob/master/demos/palette_enforcement.ipynb). The palettes are taken in by another parameter `palette`. Wallpaper uses the `WallpaperFilter` class, which automatically moves shifts the image pixels on every frame, so that the final result is seamless. ### `palette` > Default: `None` A ramp between two colors are indicated using an arrow `->`, there will be 16 shades between the two colors generated. For example: `"red->white"` Note that spaces are allowed, so that colors like `"light pink"` can be processed Multiple arrows can be used in one expression to indicate a 16 color ramp between the colors, in that order. "Red->white->black" is very different from `"black->red->white"`. Note that `"black->red->white->black"` covers all three ranks, but for four colors it seems like hell. Feels janky: use with caution. A single name of the color is equivalent to ramping that color to black. For example: `"red"` A backslash, `\`, is used to specify the number of in-between shades. For example: `"red->white\4"` Multiple elements are separated by semicolons, `;`. For example: `"red->white; green->yellow\30"` A singular color can be specified using a bracket `[]`. For example: `"red->white; [green]"` new feature: the palette can be an image or a url link. for local images, there must be a `@` in front of the filepath like `@image.png`, for webpages you need to include the `http` or `https` portion of the link. like `https://example.com/image.png` ![palettes](/files/VcUtaYBw5pEXoSYs9gRf) Another note is that when using the replicate interface, when only using single colors, encapsulate the brackets in quotation marks, but when using something else along with it, don't. For example this: ``` palette: white->black\8;[red] palette: "[white,black,red]" ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dazhizhong.gitbook.io/pixray-docs/docs/image-filters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.