Current limitations and beta limits
RasterForge is an invite-only beta. Limits may change as the app and backend capacity evolve. The account page is the source of truth for a workspace; the values below describe the default free beta plan in the current app.
Default free beta limits
| Limit | Default |
|---|---|
| Workspaces per user | 1 |
| Projects per workspace | 5 |
| Images per workspace | 20 |
| Workspace storage | 1 GB |
| Single artifact size | 100 MB |
| Artifact creates per day | 100 |
| Segmentation patches per day | 1400 |
| Render profiles per workspace | 20 |
| Segmentation profiles per workspace | 20 |
| Image examples per workspace | 100 |
| Full render longest edge | 4096 px |
| Layers per project | 60 |
| Composite inputs | 8 |
Workflow limits
- Text prompts are limited to 100 characters.
- A segmentation profile can use up to five saved examples.
- Image guidance is limited to 20 points plus boxes.
- Review currently loads images in paged batches.
- Edit works on GeoJSON Polygon and MultiPolygon objects.
- Auto masks can create many candidates; use presets and area limits to keep review manageable.
Georeferencing limits
RasterForge stores map bounds as WGS84. The bounds editor can convert common native bounds for EPSG:4326, EPSG:3857, UTM north and south zones, ETRS89 UTM zones EPSG:25828 through EPSG:25838, and EPSG:3035. Other coordinate systems may need WGS84 bounds prepared outside RasterForge.
GeoTIFF is preferred for geospatial workflows. PNG and JPEG inputs can be segmented, but they usually need manual bounds for map placement and do not carry scientific raster metadata.
Export limits
GeoPackage and Shapefile exports require selected reviewed GeoJSON outputs with WGS84 georeferencing. If a selected cell has no georeferenced GeoJSON, generate or update GeoJSON and confirm image bounds before expecting those formats.
Shapefile export supports Polygon and MultiPolygon features. Geometry that is not polygonal may need cleanup or conversion before it can be included in a Shapefile package.
Summary PDF, Summary CSV, Review ZIP, and GIS downloads use the selected image/class scope from Export. Use All reviewed when the handoff should represent the full reviewed project.
AOI and render limits
Map AOI selection needs image bounds. Standard image-coordinate AOI workflows are useful for visual inputs, but geospatial export quality depends on correct bounds. Full render size is clamped by the workspace plan, so very large rasters should use focused AOIs.
Model and cache limits
Segmentation output depends on render quality, prompt quality, examples, thresholds, Auto masks settings, and model behavior. It must be reviewed before downstream use.
Live GeoJSON recalculation can depend on stored mask bundles and cached model artifacts. If a required artifact is no longer available, rerun segmentation or create a fresh layer.
Operational expectations
RasterForge is not a replacement for human review, field validation, or domain-specific QA. Treat it as a workflow for preparing imagery, running segmentation, inspecting results, editing vectors, selecting review masters, and exporting checked outputs.