EstateAI Step by Step · Module 02: Properties · Guide 02.2
Earlier in the series: Part 01 — EstateAI Dashboard Explained
You have the property photographs ready. Before choosing an editing service, there is a more basic task: connect the right images to the right property.
The Create Property wizard is where this setup begins.
This guide follows the first two stages visible in the supplied EstateAI screenshots: Upload Photos and Property Details. It explains the available entry points, the upload status shown and the information to review before moving toward AI Analysis.
Guide scope: This is a screenshot-based walkthrough, not a recorded upload test. The later analysis, organisation and final-creation screens were not supplied. Client and property identifiers, source filenames and map details have been visibly redacted for publication; controls and workflow labels have not been recreated.
Quick answer
In the supplied interface, property creation follows this order:
Upload Photos → Property Details → AI Analysis → Review & Organize → Create Property
Start with the intended workspace and photo set. Inspect the upload information, add the relevant property details and check the location before using Next: AI Analysis.
Reaching Property Details does not mean the five-step creation process is finished.
Figure 1. The Property Details stage provides a view of the five-step wizard. The example is at Step 2, not the final creation confirmation.
1. Confirm where you are creating the property
The Properties screen covered in Guide 02.1 includes a New Property entry point. The screenshots for this guide show the setup screen titled Create Property.
At the top of the wizard, the banner reads CREATING IN — Personal Workspace. It states that the property will remain private to the user and use personal credits.
The Property Details screen also displays WORKSPACE LOCKED.
Read this context before adding the shoot. A property intended for a team should not be casually treated as a personal record without checking the selected workspace.
This screenshot does not show how to change the workspace during creation or explain the full permissions model. It also does not establish the cost of uploading, analysing or editing photographs.
Practical tip: Confirm the workspace before proceeding. Do not interpret “uses personal credits” as a price quote for a particular action.
2. Step 1: choose the property photographs
The first stage is titled Choose property photos first.
It presents a drag-and-drop area and a Select from Computer button. These are the visible local-file selection options.
The supporting text says uploading starts immediately while you complete property details. That describes the intended interface workflow; the screenshots do not measure upload speed or demonstrate what happens when a connection is interrupted.
Figure 2. A focused crop of the supplied upload screen. Surrounding capture overlaps have been excluded rather than reconstructed.
Prepare a coherent photo set
The source upload screen recommends high-resolution images, exterior photographs, important rooms and multiple room angles.
Our additional preparation recommendation is to check that the selected files belong to the same intended property and shoot. Keep a separate copy of the originals before using any editing workflow.
Do not add unrelated property images simply because they happen to share a folder.
The screenshot does not establish supported file extensions, maximum file size or a minimum pixel dimension. Follow the requirements actually shown by your account rather than assuming that every format is accepted.
Review action: Select the right source set first. Uploading more files is not the same as uploading the right files.
3. Understand the cloud-import options
Below the local upload area, an Import from section contains Google Drive and Dropbox controls.
The example also shows GOOGLE DRIVE CONNECTED.
That is a connection-status label in this account. It is not a demonstration of a successful cloud import, and it does not mean that every reader's Google Drive is already connected.
The accompanying text says imported photographs join the same upload and AI-analysis workflow as local files.
What the screenshot does not show
The provider file picker, permission request, folder-selection behavior and import-completion screen are not visible.
For a cloud-based shoot, inspect the account and files presented by the actual provider picker before confirming a selection. Do not assume that a connected-storage label means the required photographs have already reached EstateAI.
Practical tip: Treat connection and import as separate checks: the source account should be correct, and the selected files should appear in the property upload list.
4. Check the upload status in Step 2
The next supplied screen is titled Add your property details.
Above the form is a Photo uploads panel containing thumbnails, filenames and status labels. The visible example shows 39 of 39 uploaded, with Uploaded labels on the fully visible entries.
Figure 3. The upload count belongs to this example. It is neither a maximum allowance nor proof that analysis or editing is complete.
Read the count as upload progress for the displayed selection.
It does not establish that all 39 photographs were analysed, edited, grouped correctly or approved for delivery.
It also does not establish a 39-image limit.
The screen says uploads can continue in the background while details are being organised. The example itself shows a completed upload count; it does not demonstrate every possible pending or failed state.
Compare the upload list with the intended shoot
As a review step, compare the thumbnails and count with the files you meant to include.
A complete-looking counter can still accompany the wrong selection. The number alone does not tell you whether a bedroom was omitted or an unrelated exterior was included.
Review action: Check the identity of the photographs as well as their displayed upload status.
The form collects identifying details, location information and notes.
The table below preserves the visible field names. Its review advice is an editorial recommendation, not a description of hidden validation rules.
Figure 4. Field labels and the generic editing note are retained. Redaction blocks are publication edits, not native EstateAI field values.
| Visible field | What to check before proceeding |
|---|
| Property Name | Use a clear name that distinguishes this record from other shoots. |
| Property Type | Confirm the selected type. Residential is shown here; other dropdown options were not captured. |
| Client Name | Check the intended client reference before associating it with these photographs. |
| Find property address | Inspect the location selected, rather than relying only on an address-like property name. |
| City, State, ZIP Code | Check these against the intended property location. |
| Country | Confirm that it is consistent with the address. |
| MLS Number | Check any identifier you enter; the screenshot does not prove MLS integration or validation. |
| Tags | The field displays example text, Luxury, New listing. Its exact parsing rules are not shown. |
| Notes | Record useful project context without assuming that this field automatically starts an edit. |
The supplied image does not establish which fields are mandatory. Check the form's actual validation when using it; do not invent an MLS number or client detail just to fill an empty box.
Give the property a usable name
A hypothetical internal name such as Oak House — September Shoot is easier to distinguish than another Untitled property.
That is a naming suggestion, not a required format.
The property name and address are separate fields. A correct-looking name does not, by itself, confirm that the selected map location is correct.
6. Review the address and map together
The helper text beneath Find property address asks the user to choose the verified Google result.
A Property Location map appears beside the form in the supplied capture. It has been redacted in the public screenshot.
Review the address, city, state, ZIP code and country as one set. In your own account, also check whether the displayed map corresponds to the intended location.
Do not read the word “verified” as confirmation that every detail in the property record is correct. The screenshot shows a location-selection instruction, not an inspection of the property or a check of the uploaded photographs against the address.
This matters when similar street names or address-like text appear in different fields. Confirm the intended location rather than treating a populated map as the end of the check.
7. Use Notes for context, not an assumed generation command
The example Notes field contains:
Enhance and declutter etc
That records a broad editing intention. It does not demonstrate that the request has been submitted to an AI service.
A more specific note could help the person handling the job understand the brief. For example:
Example brief: Review the living-room photographs for enhancement. Any decluttering should remove only the named temporary items; retain existing furniture and permanent fixtures. Flag uncertain hidden areas before editing.
This is an editorial example, not a tested prompt or a claim that EstateAI interprets Notes in a particular way.
The service selection and settings should be checked in their own workflow. Do not treat a written note as evidence that images were processed, credits were charged or preservation instructions were automatically enforced.
8. Pause at “Next: AI Analysis”
At the bottom of Step 2, the screenshot shows Back and Next: AI Analysis.
The next button names the following stage. It is not the final Create Property action.
Before proceeding, use this short review:
| Check | What you want to establish |
|---|
| Workspace | The record is being prepared in the intended context. |
| Photos | The displayed source set belongs to the intended property. |
| Upload status | You understand the state shown for your selected files. |
| Property details | Names, identifiers and notes are accurate where entered. |
| Location | Address fields and the map point to the intended place. |
The remaining stage labels are AI Analysis, Review & Organize and Create Property.
Their actual screens were not supplied. This article therefore stops at the handoff to AI Analysis rather than claiming that analysis ran or a final property was successfully created.
Upload completion, analysis completion and final creation are different checkpoints.
Where the setup fits in the wider workflow
EstateAI by Pixel Perfects Solutions describes the property as the organising record for source images, client context, processing and versions in its product overview.
That is the product background for this setup: photos and identifying information need to refer to the same intended property.
When source photographs need professional correction, Pixel Perfects Solutions provides a separate Image Enhancement service, including white balancing, sharpening and perspective correction. That reference does not imply an automatic order or handoff from this creation screen.
For the development background, Dotera documents its work on the product in the EstateAI development case study.
These are first-party descriptions, not independent performance results.
Frequently Asked Questions
1. Do I upload photos or enter property details first?
In the supplied wizard, Upload Photos is Step 1 and Property Details is Step 2. This guide follows those screen labels. It does not assume that every product version presents an identical sequence.
2. Can I choose images from Google Drive or Dropbox?
Both options appear on the upload screen, and Google Drive is shown as connected in the example. The provider picker and completed import were not demonstrated, so account permissions and actual file selection must be checked in your session.
3. Does “39 of 39 uploaded” mean the photos are ready to deliver?
No. It reports the upload state shown for that selection. It does not prove that analysis, editing, review or final creation has finished, and it does not define a maximum photo allowance.
4. Is an MLS number required to create a property?
An MLS Number field is visible, but the supplied screens do not demonstrate its required/optional validation. Use a correct identifier where applicable and check the current form's requirements rather than inventing a value.
5. Will typing “enhance” in Notes automatically edit my photos?
The screenshot does not demonstrate that behavior. Notes should not be treated as proof of service selection, job submission or processing. Inspect the relevant service workflow before expecting an edited result.
6. What happens after Property Details?
The visible next action is Next: AI Analysis. The wizard then lists Review & Organize and Create Property. Their controls and results are outside the evidence available for this article.
Final takeaway
A useful property workspace starts before the first AI edit.
Select the right photographs. Check their upload status. Add a recognisable property name and accurate context. Review the location rather than trusting a filled field or map on its own.
Then move to the next stage with a clear understanding of what has—and has not—been completed.
Correct files, correct property, clear instructions: that is the foundation for the work that follows.
Next in the series: Guide 02.3 — AI Analysis, Review & Organize and the final creation screen.
Which setup check is easiest to overlook in your workflow: the photo selection, the address or the project notes?
Sources and screenshot notes
Figures 1–4 come from the two supplied Create Property screenshots. The upload figure is a focused crop because the original capture contains overlapping areas. No missing interface areas were reconstructed.
Client and property identifiers, source filenames and the map have been redacted. Field labels, workflow stages and displayed upload counts are retained. The screenshots' capture dates were not supplied.
The public workflow overview describes entering details before selecting photos in its summary. This guide does not silently reconcile that difference: it follows the supplied wizard, where Upload Photos comes first.
Public links were checked on September 21, 2026. The Properties app route required sign-in during verification; no upload, import, validation, analysis or billing action was performed in the account.
About the author
Waqas Ahmad writes for Pixel Perfects Solutions and supports its content, SEO and digital marketing efforts. His topics include real estate photography, AI, property-media workflows and PropTech.